Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

damage events for the posix shadow server #390

Closed
totaam opened this issue Jul 18, 2013 · 9 comments
Closed

damage events for the posix shadow server #390

totaam opened this issue Jul 18, 2013 · 9 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Jul 18, 2013

Issue migrated from trac ticket # 390

component: server | priority: major | resolution: wontfix

2013-07-18 08:31:59: antoine created the issue


At the moment we use timer-based screenscraping, I believe we should be able to re-use the damage notification approach of the regular server.

And whilst we're at it:

  • test multi-screen setup
  • keyboard: we must use the existing keymap unchanged and translate everything.. (or maybe xkbcommon can allow us to add a keyboard for each client?)
@totaam
Copy link
Collaborator Author

totaam commented Jul 18, 2013

2013-07-18 11:01:32: antoine changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Jul 18, 2013

2013-07-18 11:01:32: antoine edited the issue description

@totaam
Copy link
Collaborator Author

totaam commented Oct 17, 2013

2013-10-17 08:42:59: totaam commented


low priority - re-scheduling

@totaam
Copy link
Collaborator Author

totaam commented Jan 20, 2014

2014-01-20 11:41:42: totaam commented


Shouldn't be too hard and could make a huge difference in usability, could also use #365

@totaam
Copy link
Collaborator Author

totaam commented Mar 19, 2014

2014-03-19 11:49:25: totaam uploaded file shadow-damage.patch (6.8 KiB)

try to use x11 damage events with the shadow server

@totaam
Copy link
Collaborator Author

totaam commented Mar 19, 2014

2014-03-19 11:50:38: totaam commented


The patch above does not work... and on top of that, the few damage events it does receive show that we would often end up doing no better than we currently do with a timer!

Someone else may be interested in this in the future, re-scheduling.

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:10:46: antoine changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:10:46: antoine set resolution to wontfix

@totaam
Copy link
Collaborator Author

totaam commented Sep 27, 2016

2016-09-27 10:10:46: antoine commented


Redundant: the proper way to deal with this is #1247.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant