Re: [Pythoncard-devel] Re: [Pythoncard-users] major problem on Mac with StaticBox

[Andy T. <an...@ha...>]

Alex Tweedly wrote:
> Kevin Altis wrote:
> 
[snip]
> 
>> As for reversing the list, it seems wrong to me that the top of the 
>> list would be the "back" instead of the "front", but if other GUI 
>> builders follow that convention we could consider switching it. It 
>> isn't a trivial change unless you simply change which methods are 
>> called by the Send to Back, Bring to Front, etc. menu items and leave 
>> the list display as is.
> 
> 
[snip]
> 

The point I was trying to make is that the current terminology used in 
the resourceEditor is wrong. When I bring a widget to the front I expect 
it to be on top of the other widgets when I run my application.

To the casual user this is the expected behaviour. The order of the 
widgets in the resource file or the way they are displayed in the 
property editor is, if not irrelevant, not nearly as important.

If I send my StaticBox to the back of my background in the 
resourceEditor then I expect the widgets in front of it to trap any 
events when the application is executed. Hence when I tried to replicate 
Brad's original problem I created a StaticBox (which I sent to the back) 
and then a Button (which I brought to the front) and was confused when 
the StaticBox intercepted all of the events in the running application.

The long and the short of it is that all we need to do is swap the 
method headers in resourceEditor.py as follows;

on_componentSendBack_command <-> on_componentBringFront_command
on_componentMoveBack_command <-> on_componentMoveForward_command

This trivial change will mean that the resource editor will work in the 
same way as any other GUI builder. This can only help the casual or new 
user.

Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/