cbpporter Messages: 1401 Registered: September 2007
Ultimate Contributor
Wow!
Great!
I brought up the subject of window borders (simulating windows on a flat drawing canvas) and the support Rainbow has for this. I didn't quite understand the details of this, so now is a good time to ask again. I see that the windows have titlebars and buttons. These are managed by the specific Rainbow backend, in this case WinFB? There is code in the backend to draw window borders and handle mouse events on these borders? Simulating what normally is done by Windows or X11?
I brought up the subject of window borders (simulating windows on a flat drawing canvas) and the support Rainbow has for this. I didn't quite understand the details of this, so now is a good time to ask again. I see that the windows have titlebars and buttons. These are managed by the specific Rainbow backend, in this case WinFB?
Yes.
Quote:
There is code in the backend to draw window borders and handle mouse events on these borders? Simulating what normally is done by Windows or X11?
Exactly. Now, it is possible that if ever FB is used for embedded devices, all of this effort is a little bit overkill, as I think that on embedded, there will be no windows.
But FB is also "proof of concept" for rainbow. So I wanted to have it complete...
NOTE: Implementation-wise, those window borders are somewhat hacked solution - FB Ctrl code basically implements borderless windows with owners and TopWindow is implemented as "sort of" owned (only for internal implementation) by TopWindowFrame (but it is not visible outside of Framebuffer Ctrl implementation).
Members
Pages
Help
Register
Login
Home
