[haiku-appserver] Re: new drawing bug, Rudolf - some stuff for you :-)

  • From: Adi Oanca <adioanca@xxxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Wed, 09 Nov 2005 12:00:12 +0200

Axel Dörfler wrote:

Adi Oanca <adioanca@xxxxxxxxx> wrote:
BTW after the font stuff, I plan to work on the event handling, working my way through to RootLayer.
You mean the cursor thread and system keyboard shortcuts? You you like to explain a bit? Thanks.

Basically that, plus removing the event handling from RootLayer.

Where do you want to put it?

Also, if I find the time, I want to have a more powerful protocol between the input_server and the app_server to get things started. The way it's done now is a bit too simple, I think :)

This I don't know what you are talking about. :-)

You know what I'll be doing: clipping and redrawing stuff! :)

Okay, I won't disturb you there in the next few days :-)

You can. :-) I won't be working/in_town this weekend.

On that subject... Testing Haiku in QEmu left me a bad impression. If I move a window over another one, that one from the back won't update until I finished moving the front window. I don't like that, and that all the fault of RootLayer locking.
I think we should somehow make a region-based lock or at least make a drawing queue(in HWInterface) in which we can push drawing instructions which don't intersect with the region-selected-for-rebuild.
What do you think?

Since that doesn't happen on real hardware, I would just guess that it's because Haiku runs so slow in qemu - at least I don't remember seeing it.

Haiku running slow is a good opportunity to see some of its graphical interface defects. I think this is one of them and it can be solved. Also, on multiple CPU systems this would boost performance considerably.
I remember talking about such a thing with Rudolf. It was related to "engine_(sync/token)" IIRC.

Rudolf, can you please write a document about how you know this stuff works and how to be used. A "HowTo use engine sync token feature". I promise this is the last time I ask for this. :-)
But, please write a document we can put user version control, not explain by email.

Thank you, Adi.

Other related posts: