phosphor/src, branch v1.1.0Rust library for creating graphical programshttps://code.benbridle.com/phosphor/atom/src?h=v1.1.02024-06-08T21:56:21ZFix rendering issue2024-06-08T21:56:21ZBen Bridlebridle.benjamin@gmail.com2024-06-08T21:56:21Zurn:sha1:9dae6ee282b40b7f567f3489a8c92f08a08afbbe
I can't remember exactly what these changes were added to fix, it's
been a long time since I wrote them
Fix library version conflict errors2024-06-08T21:55:23ZBen Bridlebridle.benjamin@gmail.com2024-06-08T21:55:23Zurn:sha1:19eced3a402e1d84d06151c693b5706b2a3122ebFix scroll direction2024-05-31T22:54:49ZBen Bridlebridle.benjamin@gmail.com2024-05-31T22:54:49Zurn:sha1:2f6575f349c560a625af872adcbcb9cc82b84774
Previously, scroll values would increase in the upwards and leftwards
directions. They now increase in the downward and rightward directions.
Use geometry types forwarded by buffer2023-12-24T09:02:42ZBen Bridlebridle.benjamin@gmail.com2023-12-24T09:02:42Zurn:sha1:e2d9f83b27f894794fb4563e32a7bf8b21c15d07
Previously, this crate was defining its own set of aliases for types
from the geometry crate, which were clashing with the aliases already
defined by the buffer crate. The buffer aliases are now used instead.
Prevent crash when window dimension resizes to zero2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-12-19T08:16:15Zurn:sha1:8ad5f17d122cdd9c7ba0bb23ae6035e73ecd01de
If an application attempted to change either of the window dimensions to
zero, the surface would resize to the new dimensions and cause the window
definition in the display server to enter an invalid state, causing the
display server to crash the application.
This change ensures that the window dimensions are always greater than zero.
Redraw the window when the logical dimensions change2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-12-19T08:10:42Zurn:sha1:11c29a04f33c5611de6ec79c2e8452bece1bb952
Previously the window would only be redrawn when the physical dimensions
changed, which meant that the effects of a pixel scale change would not
be visible until the application requested a re-render.
Make window rendering code more efficient2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-12-19T08:02:55Zurn:sha1:68017c61c1ec1d0657f2e22f0d4044a955b84ccc
The code to scale the window buffer and draw it to the window surface
has been made more efficient through the use of slice::copy_from_within
and slice::fill, instead of what was slow pixel-by-pixel iteration over
long horizontal strips.
Use logical position for cursor position2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-12-19T07:59:23Zurn:sha1:1fb788cc09fa349957da501dd911435f1957c03a
Previously the physical cursor position instead of the logical cursor
position was being passed to WindowController::on_cursor_move, which
meant that the cursor position that the application was receiving would
be incorrect when the window scale was greater than 1.
Use pixel scale as window resize increment2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-12-19T07:52:42Zurn:sha1:8e019fb17d49dd1d605e81a59a84febfd4fc41c8
When resizing a window, the window width and height will be made to be a
multiple of the current pixel scale. This is to prevent thin black strips
from rendering along the bottom edge and the right edge of the window
when the dimensions of the window exceed the dimensions of the scaled
screen content.
Specify frame limit as FPS instead of as frame time2023-12-19T08:17:35ZBen Bridlebridle.benjamin@gmail.com2023-11-05T02:25:29Zurn:sha1:6b6bd38e84d1d14a526765bd23926024b2eda3c7