- Mar 15, 2021
-
-
Jonathan Wilkes authored
Fix - Punctuations See merge request jwilkes/purr-data!614
-
-
- Jan 25, 2021
-
-
Jonathan Wilkes authored
-
- Jan 19, 2021
-
-
Jonathan Wilkes authored
Not sure what this was used for. Could have been a remnant from ancient Pd-extended builds where libdl was required to dynamically load at all, but that's a shot in the dark. Anyway, if we get reports in a future release of some external randomly refusing to load under Windows, we may want to test whether this change is the culprit.
-
- Jan 18, 2021
-
-
Jonathan Wilkes authored
-
- Jan 11, 2021
-
-
Jonathan Wilkes authored
-
- Jan 02, 2021
-
-
Jonathan Wilkes authored
-
- Jan 01, 2021
-
-
Jonathan Wilkes authored
-
- Dec 31, 2020
-
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
- Dec 29, 2020
-
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
- Dec 28, 2020
-
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
- Dec 23, 2020
-
-
Jonathan Wilkes authored
-
- Nov 24, 2020
-
-
Jonathan Wilkes authored
-
- Nov 22, 2020
-
-
Jonathan Wilkes authored
-
- Nov 02, 2020
-
-
Albert Gräf authored
-
Albert Gräf authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
- Nov 01, 2020
-
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
- Oct 31, 2020
-
-
Jonathan Wilkes authored
-
- Oct 30, 2020
-
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
-
Jonathan Wilkes authored
This gives what is to me smoother and more predictable snapping motion with respect to the current mouse position. For example-- imagine the grid cell size is 10 and the selected object under the mouse already has its top left corner aligned with vertical grid line #2. If I begin dragging that object to the left, within a single pixel of motion it will snap to vertical grid line #1 which is 9 pixels away from the object's current position. With this commit, the user must drag the object cellsize / 2 pixels before it snaps to a new position. To me this seems smoother as it rounds to the nearest grid line rather than to the grid line with the smallest coordinate value.
-
Albert Gräf authored
-
- Oct 29, 2020
-
-
Jonathan Wilkes authored
We also keep a partially transparent version of a grid for editmode. This allows us to keep editmode visually distinct from runmode, even if snap-to-grid isn't turned on. If needed it's pretty easy to make the following changes: * set the "big" cell size to something that isn't 100 (but I'm not sure how much control over the grid we actually want to give users-- e.g., setting the big cell to something for which the small cell isn't a factor * allow snap-to-grid to be set independently for each canvas. (But again, what would be the use case for this?
-
- Oct 24, 2020
-
-
Albert Gräf authored
-
Albert Gräf authored
also run for extended periods of time.
-
Albert Gräf authored
For some reason, GUI operations which run for extended periods of time may cause the engine to crash with a SIGHUP error on Linux. Apparently this is caused by the watchdog bailing out and taking the engine with it. This affects the new print operation as well as the existing message operation in the file menu, possibly also search index generation for the help browser, and maybe some other operations that still need to be identified. The new gui-busy method lets the GUI set an internal flag in the engine which makes the engine keep the watchdog happy while the GUI does its thing, using the same mechanism that is already in place to ping the watchdog when running GUI-less. To these ends, the GUI needs to invoke "pd gui-busy 1" when starting the time-consuming operation, and "pd gui-busy 0" when the operation is done.
-
Albert Gräf authored
-