Advertisement
Guest User

Untitled

a guest
Jun 28th, 2017
54
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.25 KB | None | 0 0
  1. <Megz> will Wayland be absolutely immune to the "nasty queue" problems that Xorg has?
  2. <Megz> The nasty queue worked like so...
  3. <Megz> Pick some app, Take the corner of it and resize it quickly, move your mouse all around fast
  4. <Megz> You can see all kinds of intermediary updates of a queue of events catching up
  5. <ajax> no.
  6. <Megz> wayland will not be immune to that? why?
  7. <ajax> because that's not something you can be immune to. you've got an event stream and the app has to catch up.
  8. <Megz> ajax, it doesn't happen on MacOSX or Windows in any perceptible way
  9. <ajax> it's nice that you think that.
  10. <Megz> Try it next time with Google Chrome on win32
  11. <Megz> you can drag it around fast, but the queue is imperceptible
  12. <ajax> that's not the same as "it's not there"
  13. <Megz> there is a key difference. resizing chrome on win32 has a "constant factor" that the events get serviced and stuff happens. you cant see anything is wrong because it's so constant.. but the difference with Xorg, was that Xorg would get Stuffed-up
  14. <Megz> stuffed-up in that the more events you made, the worse it gets, quickly
  15. <Megz> it was never constant. one thing would block another thing from being able to update in the next frame, and it would all turn out as being highly perceptible
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement