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

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

Alex Tweedly wrote:
> Andy Todd wrote:
> 
>> The point I was trying to make is that the current terminology used in 
>> the resourceEditor is wrong. 
> 
> I disagree that the terminology 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.
>>
> That's what I currently observe happening.
> 
> If I bring a component "to the front" then (when the app is run) it 
> appears at the front (i.e. on top of other components). If I send it to 
> the back (and run the app) then it (dis)appears behind them.
> 
>> 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.
>>
> Forget the internals :
> 
> I created 4 overlapping buttons:
> I selected button1 and brought it to the front
> Then button2 and brought it to the front
> then button3
> then button4
> 
> then saved the file, and did File/Run
> 
> 4 in front
> 
> Then I selected button3 and brought it to the front, saved, and ran it.
> 
> 3 in front
> 
> then selected button2, brought it to the front, saved and ran that.
> 2 in front
> 
> 
> So, as I said, I see it as already behaving properly.
> 
>> 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.
>>
> Unfortunately, on Win, the button produces events whether it's in front 
> or behind - so I can't reproduce this at all.
> Is the button inside the box ? Or overlapping the box border / text ?
> 
>> 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.
> 
> I think it's more complicated than that.
> Do you see the same overlapping with buttons as I see on Win ?   Or is 
> that also different ?
> 
> -- 
> Alex Tweedly       http://www.tweedly.net
> 
> 

Just FYI, here's how your sample appears on Mac OSX 10.3 with Python 
2.3, wxPython 2.5.3.1 and PythonCard from CVS.


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