phosphor, branch v3.0.0Rust library for creating graphical programs
https://code.benbridle.com/phosphor/atom?h=v3.0.02024-10-28T06:59:15ZUpdate version to 3.0.02024-10-28T06:59:15ZBen Bridlebridle.benjamin@gmail.com2024-10-28T06:59:15Zurn:sha1:47a754a7beb8741bfe0469236036cb8023043cd8Complete rewrite of Phosphor2024-10-19T05:21:48ZBen Bridlebridle.benjamin@gmail.com2024-10-19T05:20:09Zurn:sha1:990f2b310bfecf2e04a8a462f6939833080c62bf
The previous version of the library passed events to an implementation
of a WindowController trait by calling the trait method associated with
each event, and received requests by calling different trait methods and
reading the returned values. This had the downside of requiring that any
data received from one event had to be stored in the type so that it
could be passed back to Phosphor when a request method was called.
The new library structure uses a single handle_event method on a trait,
which is passed data representing any single event when it is called.
Data is returned via a passed mutable reference to an EventQueue,
meaning that any number of responses for any event can be immediately
returned to Phosphor without having to wait in storage.
Fix issue with damaged screen not being redrawn2024-09-10T00:48:13ZBen Bridlebridle.benjamin@gmail.com2024-09-10T00:46:56Zurn:sha1:824483fc95ccbc4627d07371bac8ed4da44c83e7
When another window was dragged over a Phosphor window, the Phosphor
window would have streaks drawn over it from the dragged window and
would need to be redrawn. This was handled by an unrequested render
request, where a render request is received that was sent not by the
program itself but by Phosphor.
These unrequested requests were being ignored due to commit 30c61fd,
because of an issue on Windows where programs were receiving upwards of
50 unrequested requests per second for no reason, which was impacting
program performance. They have been re-enabled, pending an investigation
into the cause of these requests on Windows.
Update version to 2.0.02024-08-10T02:35:06ZBen Bridlebridle.benjamin@gmail.com2024-08-10T02:35:06Zurn:sha1:d598b9b0b404b386c460a09933bcfce4683b8f7aUnify is_cursor_visible and cursor_icon callbacks2024-08-04T04:18:24ZBen Bridlebridle.benjamin@gmail.com2024-08-04T04:18:24Zurn:sha1:c141d8fe8bb9115ccb953ed6ea5b0b04bc828125
It makes sense to handle all cursor icon state at once.
Fix display server lag2024-08-04T04:11:18ZBen Bridlebridle.benjamin@gmail.com2024-08-04T04:11:18Zurn:sha1:e85f41bdf72b31f6d9224cb0d9f71986cc12a15e
This commit reverts commit 3d44c40. Calling window.title() was causing
the X11 display server to go from 1% to 20% constant CPU usage when
testing on Linux.
Improve comment clarity2024-07-31T04:06:43ZBen Bridleben@derelict.engineering2024-07-31T04:06:43Zurn:sha1:8d626d526cbf27b02896af82979a090c0b768a7dSimplify code2024-07-31T04:06:25ZBen Bridleben@derelict.engineering2024-07-31T04:06:25Zurn:sha1:3d44c407c5c6c5574f6d3f272c6651fd75e07deb
We don't need to keep track of the previous value of the window title.
Implement fullscreen2024-07-31T04:05:57ZBen Bridleben@derelict.engineering2024-07-31T04:05:57Zurn:sha1:efe1d21b0e1ee79ef7547c0d8524a39be16ccc7d
Program windows can choose to show as fullscreen or windowed.
Only set window title when changed2024-07-31T03:36:53ZBen Bridleben@derelict.engineering2024-07-31T03:36:53Zurn:sha1:20bc849cfd990267684532d84b9894204c96189f
Setting the window title every frame was causing Windows Explorer to
show a consistent 4% CPU usage when testing under Windows 10. This
change brings it down to 0.2%.