Re: [Pythoncard-devel] possible Raise/Lower workaround for resourceEditor

[Kevin A. <al...@se...>]

On Dec 23, 2005, at 6:16 PM, Kevin Altis wrote:

> See my "Re: ignore Raise/Lower comment for now" message at:
>
> http://news.gmane.org/gmane.comp.python.wxpython.devel
>
> What I'm still not sure about is why the resourceEditor widget 
> reordering doesn't appear to work on Windows or the Mac. I'm going to 
> dig further and see where we broke this since it should at least do 
> the right thing on at least one of the platforms. So far it appears 
> that fixComponentOrder is not actually being called when it should be 
> which certainly is a problem, so I need to figure out when and why 
> that was changed.
>
> ka

I think I may have got it. As far as I can tell, Lower() doesn't always 
work, but Raise() does, so I simply changed the code to do a little 
extra work...

     def fixComponentOrder(self, name):
         # KEA 2005-12-23
         # Lower() doesn't appear to always work correctly,
         # so use Raise instead with a reversed list
         r = self.components.order[:]
         r.reverse()
         for c in r:
             self.components[c].Raise()
...

Since fixComponentOrder is always called this appears to work correctly 
on the Mac as well. I'm still tempted to call Lower() on the Mac when a 
component is created in model.py but that is a separate issue. Anyway, 
I'll let this sit for a bit, so let me know if you notice any behavior 
that seems wrong. I don't want to start changing code to reverse the 
Property Editor list or change the current Front/Back semantics until 
we know this works correctly. I'll assume the developers are still in 
favor of reversing the Front/Back semantics, so I'll look at that next.

ka