From: Kevin A. <al...@se...> - 2001-08-21 20:01:02
|
I made the Property Editor a "listener" of the background components so now when you add or delete a widget, the change should be reflected in the Property Editor. This makes the Property Editor usable with the resourceEditor. When you select a widget in the resourceEditor, it automatically selects that component in the Property Editor. I think I fixed the backgroundColor reset problem when opening up a stack. The default background color appears to be the wxPython constant wxSYS_COLOUR_3DLIGHT but I haven't tried using many color schemes to see if this is always correct. The real problem is that when you pass a wxNullColour to wxPython it doesn't automatically use the correct background and foreground colors. I think this is a bug, but if the behavior of wxWindows/wxPython isn't going to change, we'll need to special-case the default color when the user specifies a color of 'none'. There is a bug that I haven't been able to solve yet that occurs when you have a widget selected and then open a different .rsrc.py file that has a widget with the same name; this would most likely be a reload of the currently open .rsrc.py file. What I think is happening is that a mouse event is occurring when you select the file in the Open File dialog and somehow that is being sent to the background. In between hiding the sizing handles, deleting old widgets and creating new ones, the widget ends up getting moved and a KeyError is generated when accessing the list. I'm still investigating, but if you have any ideas let me know. ka |