[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk-devel
Subject:    Re: Intricate changes to Quartz/OSX backend
From:       John Ralls <jralls () ceridwen ! us>
Date:       2009-10-26 22:21:04
Message-ID: B6D0AF1E-3C10-42A6-8126-D8A7C29DE0D0 () ceridwen ! us
[Download RAW message or body]


On Oct 26, 2009, at 9:00 AM, Kristian Rietveld wrote:

> On Oct 26, 2009, at 4:50 PM, John Ralls wrote:
>> On Oct 26, 2009, at 8:36 AM, Kristian Rietveld wrote:
>>
>>> On Oct 26, 2009, at 3:03 PM, John Ralls wrote:
>>>> I'll pull & build for SL this morning. What particular dual- 
>>>> monitor behavior should I look for?
>>>
>>>
>>> I have verified that it builds fine on SL.  Things that might be  
>>> broken are event delivery on the secondary monitor (or on the main  
>>> monitor if the menubar is on the secondary), broken menus, broken  
>>> window placement, etc.  If you find no regressions, then awesome :)
>>
>> What do you mean by "event delivery"? That mouse-clicks in a window  
>> on the secondary monitor don't do anything?
>
> Yes for example.  As well as missing motion and crossing events.

OK. I ran through several of the tests in gtk-demo. I found a crasher,  
but it's not a regression. (Both of the "Off-screen Window" demos  
crash on launch, in the same place; backtrace is below. I haven't yet  
figured out what's going on with it.)

So the only difference in behavior that I see is that the windows open  
on the secondary screen instead of the primary one. Dragging them  
around works either way.

Regards,
John Ralls




(gdb) bt
#0  0x9706691b in objc_msgSend ()
#1  0x048240c0 in ?? ()
#2  0x001ce6b1 in gdk_window_process_updates_internal  
(window=0x30319e8) at gdkwindow.c:5218
#3  0x001ce8cc in gdk_window_process_all_updates () at gdkwindow.c:5326
#4  0x001ce064 in gdk_window_update_idle (data=0x0) at gdkwindow.c:4952
#5  0x001a2c4e in gdk_threads_dispatch (data=0x482cc00) at gdk.c:506
#6  0x026b3dc0 in g_idle_dispatch (source=0x2b44830, callback=0x1a2bf9  
<gdk_threads_dispatch>, user_data=0x482cc00) at gmain.c:4065
#7  0x026afe25 in g_main_dispatch (context=0x2b10600) at gmain.c:1960
#8  0x026b136d in g_main_context_dispatch (context=0x2b10600) at  
gmain.c:2513
#9  0x026b1877 in g_main_context_iterate (context=0x2b10600, block=1,  
dispatch=1, self=0x2b10930) at gmain.c:2591
#10 0x026b2069 in g_main_loop_run (loop=0x4033380) at gmain.c:2799
#11 0x0094e71b in gtk_main () at gtkmain.c:1218
#12 0x000279ed in main (argc=1, argv=0xbffff4b0) at main.c:1010
(gdb) f 2
#2  0x001ce6b1 in gdk_window_process_updates_internal  
(window=0x30319e8) at gdkwindow.c:5218
5218              _gdk_windowing_window_process_updates_recurse  
(window, expose_region);
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic