Re: [Pythoncard-users] Re: PythonCard suitability for a project; looking for opinions

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

On Sep 15, 2004, at 6:07 AM, normanwinn wrote:

>
> A pretty neat design trick in Filemaker might be easily added to the=20=

> PythonCard resource editor. When an object is selected the arrow=20
> buttons move the object a pixel (or grid position) at a time.

Yeah that was on the to do list, so I just added it and checked the=20
change into cvs. It supports 1 pixel movement right now. I didn't feel=20=

like grappling with the calculation to figure the right relative grid=20
jump before I had some coffee, but I'll look at that later ;-)

> If I manage to get my Python up to speed I'd like to try to generate=20=

> the function definition header directly in the code by double clicking=20=

> the item or event in the resource editor - =E0 la Delphi. Good or bad=20=

> idea?
>

This is another topic that has been brought up before. Since the=20
resourceEditor doesn't deal with actually editing the code yet, events=20=

are not part of the attribute list since the assumption is that people=20=

will be using the codeEditor or some other editor to manipulate the=20
source code.

There is a codeEditorR.py program based on the codeEditor that has an=20
additional experimental feature. When you are editing a source file, it=20=

reads the associated .rsrc.py file and provides a dropdown menu of all=20=

the components. When you select one of the components from the menu, it=20=

populates the second dropdown menu with a list of all the events for=20
the component type. The events that are already defined have a + in=20
front of the name. If you select an item with a + in front, the cursor=20=

jumps to that event handler in the code. If you select an event that=20
isn't in your code, then an event handler stub for that event is=20
inserted at the current cursor location.

ka