Re: FruitMenu & X11
Re: FruitMenu & X11
- Subject: Re: FruitMenu & X11
- From: Matthew Klahn <email@hidden>
- Date: Thu, 29 May 2003 12:41:23 -0500
On Thursday, May 29, 2003, at 12:27 America/Chicago, Torrey T. Lyons
wrote:
At 11:49 AM -0500 5/29/03, Matthew Klahn wrote:
I've spkoken (via email) w/ tech support at unsanity and they have
informed me that FruitMenu is tha cause of the X11 crashes i've been
experiencing. If anyone else out there is having this problem, this
is
why. If anyone out there has found some work-around, please please
tell
me! :-D
Thanx, JP
I don't run FruitMenu right now, but have tested our own stuff
against it in the past; we had a problem where FruitMenu was
attempting to add stuff to some contextual menus in DockExtender that
would crash it. I wonder if you add X11 to FruitMenu's ignore list
(available via the FruitMenu prefPane) if that would solve your
problem? That did solve the problem for DockExtender until we changed
the code to prevent the crash from happening.
I would be very interested in know more details in how you changed the
code to prevent FruitMenu from crashing your app. All flavors of
XDarwin and X11.app crash with FruitMenu active and we (the XFree86
project anyway) would like to work around this problem to eliminate
this recurrent question.
--Torrey
XFree86: "Saving the world one pixel at a time."
Hi, Torrey.
The problem was that FruitMenu was attempting to add items to
DockExtender's internal contextual menus. DockExtender would then later
(through a Carbon callback) step through the menu and replace
placeholder items in submenus with the expanded contents of the submenu
for a do-it-your-own dynamically loading submenu. When we attempted to
step through the menu contents, we would change the size of the menu,
and since FruitMenu had inserted items into the menu, we could crash
the program by steping out of the menu's bounds. To solve this, we
overrode the menu class & kept our own state on how many items there
should be. We then, before expanding the submenus, would strip out the
inserted FruitMenu menu items since they were always the last items in
the menu, beyond the number that we knew that we were supposed to have.
Now, I can't say that this is helpful to you guys at all, but this is
what was happening to us. But, if inserting the X11 application into
FruitMenu's ignore list doesn't help, then I don't know of a solution.
If you talk to the unsanity guys, perhaps they could add your X11 (or
XDarwin) application to the default ignore list? They're great guys and
should be willing to help...
As far as we could tell, there was no way to prevent FruitMenu from
attaching to DockExtender, other than the ignore list.
--
Matthew S. Klahn
Software Architect, CodeTek Studios, Inc.
http://www.codetek.com
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.