Re: [Pythoncard-users] Resource Editor bug (?)

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

On Sep 17, 2006, at 2:25 AM, Jussi Salmela wrote:

> And the plot thickens...
>
> I've been playing a little with the multipropertyEditor changing the
> place in question to look like this:
>
<snip>

I checked in a new version of propertyEditor.py for the  
resourceEditor at:

http://pythoncard.cvs.sourceforge.net/pythoncard/PythonCard/tools/ 
resourceEditor/modules/propertyEditor.py?view=log

You can see the diffs with:

http://pythoncard.cvs.sourceforge.net/pythoncard/PythonCard/tools/ 
resourceEditor/modules/propertyEditor.py? 
view=diff&r1=text&tr1=1.57&r2=text&tr2=1.56&diff_format=h

This change may not totally solve the problem and I moved the  
discussion to pythoncard-devel for a more elaborate fix. In addition,  
Alex will need to roll these same kinds of changes into his  
multipropertyEditor. The basic idea is that attributes which are  
supposed to be strings such as command shouldn't get an eval()  
anymore, while attributes that are numbers, lists, tuples, etc.  
should be handled by eval. All attributes that are edited in a text  
field must be converted to strings before they can be displayed and  
edited by the user, so eval or an explicit conversion based on  
expected type must be done when the user is done editing.

I did very little testing of this "fix" so feedback from anyone that  
wants to try it would be appreciated.

ka