Sorry again for RE-Disturbing you, but I got no replies on this message
and it was posted more than a week ago (maybe it didn't got to the list
cos I was doing silly things with my mail system at the time)...

Would you tell me what you think? (or simply a yes or no to do it...)

Thanks and sorry again.

On Wed, 12 Jun 2002 19:14:26 +0200
"Julio Merino" <jmmv@hispabsd.org> wrote:

> Hello
> 
> When I posted some time ago my mouse daemon patch, some of you argued that it
> didn't address some possible problems:
> 
> 1) What happens if the user switches console while selecting text?
> 2) How to manage X + console access to the same wsmouse device?
> 
> Well, I think I've found a clean solution which still allows the wsmoused daemon
> to live entirely in user-space. That is, we may add a new pseudo-device, for
> example /dev/wscons, where kernel injects events like "hey, user has changed
> current console to number n", or "notice that user has changed to a X display".
> 
> Then, the wsmoused daemon would read from that device with a select() and take
> proper actions when an event of this kind happens. If user changes current
> console, then the daemon should restart the selection from the current point.
> If the user changes to a X server, then the daemon should close wsmouse device
> to allow X work with it, and when the user comes back to consone, reopen the
> device.
> 
> What do you think? Can I go an implement this kind of pseudo-device if none of
> current existing ones can suit this problem?
> 
> Thank you.
> 
> -- 
> HispaBSD admin - http://www.hispabsd.org
> Julio Merino <jmmv@hispabsd.org>


-- 
HispaBSD admin - http://www.hispabsd.org
Julio Merino <jmmv@hispabsd.org>