From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52921) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIKqT-0006AN-4R for qemu-devel@nongnu.org; Wed, 20 Mar 2013 11:22:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIKqO-0002k3-Fo for qemu-devel@nongnu.org; Wed, 20 Mar 2013 11:22:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:15798) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIKqO-0002jp-6s for qemu-devel@nongnu.org; Wed, 20 Mar 2013 11:22:24 -0400 Message-ID: <5149D42C.9030404@redhat.com> Date: Wed, 20 Mar 2013 16:22:20 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <1363772625-9182-1-git-send-email-kraxel@redhat.com> <1363772625-9182-23-git-send-email-kraxel@redhat.com> <87d2uu6x3z.fsf@codemonkey.ws> In-Reply-To: <87d2uu6x3z.fsf@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 22/23] gtk: show a window for each graphical QemuConsole List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org On 03/20/13 14:04, Anthony Liguori wrote: > Gerd Hoffmann writes: > >> Multihead support: For each graphical console we'll create a gtk >> window, so with multiple graphics cards installed you get a gtk window >> for each. vte tabs are attached to the console #0 window. > > This is neat but I'm not sure if the user experience is right. > > Each window would have independent grab. Each window would have > independent full screen. > > I'm not sure there's an obviously right solution but it's worth > discussing. I do like the idea of having two windows but perhaps we > should make the second window have a no menu bar with a title that > indicates that it's a secondary display? Sure there is plenty of room for improvements, but I think those can go in incrementally ... /me went for another window because placing the secondary display into a tab doesn't make that much sense, and this is the minimal patch doing just that. It's also not really usable (yet) anyway as we don't have input routing, atm there is absolutely no way for the guest to figure which display (absolute) mouse events where coming from. cheers, Gerd