Re: [Pythoncard-users] added Duplicate Widget to resourceEditor

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

I've been playing with this over the last couple of days and its looking 
good to me.

Kevin Altis wrote:

> I added a Duplicate Widget menu item and command. I also cleaned up the
> mouseDown selection code.


The duplicate widget works as expected but if we are going to place the 
new widget in the same location as the original (instead of, say, offset 
by a few pixels) then can we have the new widget on top please?

My expectation (from using similar techniques in other products) is to 
be able to duplicate a widget and then drag the new one to the location 
I want it to be in. This may be beyond us at the moment, if so I will 
add it to SF as a feature request so we don't forget.

> 
> Overall, it seems to be working pretty well, so I'm tempted to have it start
> saving files. Nobody has said whether the selection and resizing is working
> correctly on *nix. Any bugs to report on any platform?


Not from me. I'd love to be able to save resource files but I can I 
suggest the default behaviour is to not override an existing file? Not 
sure how we can do this with the wx file dialog but I can live in hope 
(or read the documentation).

> 
> Any other feedback? I realize that there are all sorts of things it doesn't
> do like Undo/Redo, Cut, Copy, Paste, multiple selections, etc. but it seems
> quicker and easier than hand coding all the component descriptions. I need
> to set the stack and background attributes, which is going to be clunky
> until we have more elaborate dialogs up and running, so I lean towards still
> editing those by hand in the .rsrc.py file, I would simply save some generic
> values for new .rsrc.py file.


That would seem the sensible approach. Of course, in PythonCard 1.0 we 
will provide a wizard to guide you through this and then have an 
application property sheet when these values can be changed.

> 
> One issue that I don't have a ready solution for is that I won't be able to
> preserve the original formatting of a .rsrc.py file when I do a save. Does
> this matter to anyone? I'm leaning towards an output format where each
> attribute of the stack, background, and components are on a separate line
> which will avoid problems with wrapping when people paste portions of a
> .rsrc.py in email, etc.


I think we would have to assume that if people are saving a resource 
description from the editor they would want a working file output. An 
alternative would be to provide a preview option showing the resource 
file to be output before it is saved. Then the hard core developer could 
just cut and paste the bits they want from the previewer to their own 
resource file.


> 
> I have some code that I wrote a while ago that imports Outlook contacts that
> I could turn into an Addresses sample. Other people could add import code
> for other formats. Perhaps I'll create that sample using the resourceEditor
> as a test later this week.
> 
> ka
> 

Regards,
Andy
-- 
-----------------------------------------------------------------------
 From the desk of Andrew J Todd esq.
"Shave my poodle!"