1) I think that the "seat" part of a multiseat system can be merged into the "computer" part as far as the GUI is concerned. So I don't think there's need to add extra label options, only to put the seat name/number as a suffix after the computer name.
2) Each of those root terminals has access to a different display, that of the user sitting in that seat. So if the epoptes user selected many seats and clicked on that menu, maybe he wants to do something with each seat separately, we can't assume that he only wanted one terminal even though he selected many... The worst problems with multiseat are that (a) there are many different implementations and (b) the developers have no access to any multiseat system to test with. So we have no clue about how the seats are named, if they're static or dynamic etc. It'd be nice if there was some person with access to multiseat systems that could contribute code patches. -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/980141 Title: some more suggestions for dealing with multiseat environments Status in Epoptes: New Bug description: I'd like to suggest some changes in Epoptes to work better with multiseat environments: 1. Add label options "Computer:Display (User)" and "Computer:Display" to "Labels" menu. 2. When lauching "Root, locally" terminals for several seats simultaneously, launch just one terminal for each computer, not one for each user. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/980141/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
