Re: [Pythoncard-devel] request for additional comments for changelog.txt

[<bra...@om...>]

> Kevin Altis wrote:
> 
> >
> > Thanks Alex. readme.txt should be adequate for both of the new apps. 
> > Do you think multiresourceEditor should have a shortcut in 0.8.2 or 
> > wait another release?

Alex Tweedly replied:

> I think it could have one now - I have no outstanding bugs I'm aware of, 

> and although I couldn't claim to have "tested it thoroughly" on Python 
> 2.4 / wxPython 2.6.1, I have given it a fair work-out over the last 
> couple of days and seen no problems.    (That is, of course, ignoring 
> all the raise / lower issues ..... which I don't think are any different 

> in the multiresourceEditor)
> 
> (I did discover one problem with the tabcodeEditor - report coming 
> shortly unless I stumble into understanding it myself ....)


MultiResourceEditor has been very robust for me. I've used it regularly
for the past few months. It's not perfect--for instance, I wish the Vary 
checkbox
defaulted to "off" and was renamed to something more obvious 
"Auto-Naming".
But's that just my preference, not a bug. There are probably bugs I 
haven't 
noticed, of course, since I only use 14 out of the 25 widgets available.

I haven't used the old Resource Editor in a long time. MultiResourceEditor 
is
just too useful for me to consider going back. It's great to be
able to see all the properties for a widget displayed simultaneously,
and for that matter it's also frequently useful to be able to select
multiple widgets simultaneously. 

The old Resource Editor also had a number of frustrating glitches in 
relation
to moving and resizing objects. Alex fixed those issues for 
MultiResourceEditor.

Overall, I think the MultiResourceEditor puts a better face on PythonCard
and is less likely to scare off newbies.