From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dlc8C-0006Z6-Mh for qemu-devel@nongnu.org; Thu, 23 Jun 2005 20:33:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dlc8A-0006Xt-5x for qemu-devel@nongnu.org; Thu, 23 Jun 2005 20:33:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dlc89-0006Xc-Gc for qemu-devel@nongnu.org; Thu, 23 Jun 2005 20:33:13 -0400 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DlcAZ-0007w5-Ec for qemu-devel@nongnu.org; Thu, 23 Jun 2005 20:35:43 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j5O0WBcl020155 for ; Thu, 23 Jun 2005 20:32:11 -0400 (EDT) Date: Thu, 23 Jun 2005 20:32:08 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] quick gtk2.c update Message-ID: <20050624003208.GA22540@jbrown.mylinuxbox.org> References: <20050622205920.GA31106@jbrown.mylinuxbox.org> <003501c5779a$f523a4f0$334d21d1@organiza3bfb0e> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003501c5779a$f523a4f0$334d21d1@organiza3bfb0e> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wed, Jun 22, 2005 at 09:26:11PM -0500, jeebs@yango.us wrote: > "Jim C. Brown" > > > > Ok this is probably the final revision. I had the code vindicated by an > > actual > > Windows programmer. He says it should work fine. It should compile, run, > > and make > > Okay... I compiled it and the keys do appear to work. > > That problem does appear to be fixed. > Excellent news. > It doesn't look like the 'insert' key toggles between insert / overstrike > when I use the Win3 wordpad to read a file. However, this is in the regular > qemu 0.70, so I don't know if it's a problem with qemu, or Win 3 wordpad. > I don't have a copy of Windows 3 (3.0, 3.1, WfW, or 3.11), so I am not able to test this. Windows 98 Wordpad has no issues with the insert key for qemu-gtk. > Now, while running my Win 3 test image, I notice that double clicking > doesn't work. I couldn't get anything to open up no matter how fast I > clicked. > > Single clicking works okay, though. > Again, I can't test Windows 3. However, under Windows 98 double clicking does seem to have problems. It does work for me ocassionally (if I keep clicking hard and fast enough - more "stream clicking" than double clicking), but there are clear issues. The way GTK/GDK deals with single, double, and triple clicks is weird. I'll take a much closer look at it. > > > qemu under gtk usable. Also I modified it so it lets u know when u are > > using GTK. > > I noticed that immediately when I ran it... Nice. Thanks. > Never a problem. Like I said, it was a dumb oversight on my part. > > Still, I work with what I have to go on. Try this gtk2.c and report any > > errors > > (be they compile errors or runtime errors or keyboard problems). Your help > > is > > always greatly appreciated. > > I'm glad I'm able to help. > > The previous qemu errors I've reported have been completely ignored! > > At least you are taking an active interest in what a mere user has to > say.... > I don't think that I am exceptional in this. Most developers are happy to fix bugs that users report (time permitting of course). It simply looks like qemu is lacking dedicated Windows developers. At least, thats how it looks to me. I know of only 1 real developer of qemu under windows. But he works on a separate tree (C code cleaned up to compile under MSVC, different IDE and VGA/ Cirrus code, etc). -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.