Originally posted by smitty3268
View Post
Announcement
Collapse
No announcement yet.
Qt 5.1 To Feature Improved Support For Wayland
Collapse
X
-
Originally posted by smitty3268 View PostThere is a way to tell that applications are not responding (or otherwise something like a busy cursor wouldn't be possible).
Comment
-
Originally posted by liam View PostLast time I looked they were supposed to be using polling to determine if windows were responsive or not (I believe this works the same way as in android).
Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)
Comment
-
Originally posted by curaga View PostYup, one of the worst techniques to do anything in computing.
Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)Last edited by newwen; 31 January 2013, 11:21 AM.
Comment
-
Originally posted by curaga View PostYup, one of the worst techniques to do anything in computing.
Just like sending commands is always better for network use than sending pixmaps (scraping pixels, VNC-style), polling is just about always the worst possible solution. But it's probably the only possible one, forced by Wayland's design, just like the pixel-scraping for networking (or the other proposition, per-toolkit thing which nobody will implement, or with which every toolkit will be incompatible with each other. Seriously, it's a huge advantage to have network support for *every* app by default, not just those compiled with toolkit foo.)
I wouldn't argue about polling being a bad idea in general but sending commands isn't the best way for dumb retinal situations. Additionally, I don't know how well sending 3d commands would work from a performance POV.
I'm not sure polling is there only option. Heck I'm not sure they settled on it. Only that it seemed to be the path they were going to use first.
Hopefully there will be an fdo proposal made for sending drawing instructions across networks for those who want it but I'm fine with sending diffs.
Comment
-
Originally posted by smitty3268 View PostLink, or please explain why the simple process above won't work.
Check the Wayland video from the last Xorg conference, you genius! Michael recorded the entire conference and the videos were heavily featured and yet you missed that?
Comment
-
Originally posted by Awesomeness View PostI did research. Wayland will only allow to kill unresponsive apps, not allow to minimize them.
ONLY kill unresponsive apps?
The display server that would later be called Weston has supported moving frozen windows since at least 2010!
Comment
Comment