🚀 go-pugleaf

In article <4j9tk9$3ne@mongol.sasknet.sk.ca> bruce@rpl.regina.sk.ca (Bruce Welch) writes:
[ chooser lockups ]
>My $.02 on this one.  It depends on where you click!!  If I click on the 
>main bar - freeze = solid.  If I click on the << button - works every 
>time.  At first I thought it was related to cycletomenu, but removing it 

Chris Aldi has put a lot of work into fixing this problem. Personally,
I haven't seen it since the early days of ClassAct, months ago. The
problem is stack. Since input handling happens in input.device, a
complex BOOPSI gadget such as chooser can take quite a bit of stack,
and input.device only has very little of it available. Since chooser
opens a borderless window when you click on the "main bar", any hacks
that affect OpenScreenTagList() stack usage will also risk a crash
here. A future version of chooser will most likely switch the
input.device stack to a larger one for the duration of chooser input
procession to avoid this problem.

-- 
Maybe I was holding all the aces, but what was the game?
| "Osma Ahvenlampi" <mailto:oa@iki.fi> <http://www.iki.fi/oa/> |
| Amiga&BeBox&ClassAct&Voodoo&ARTech cool stuff: I-Net225&AWeb |
                                                              --