PythonCard

> From: andre rutti
>
> Hi,
>
> I'd like to have horizontal scroll bar in a TextArea component.
> Is this possible? and how.
>
> Thanks and regards,
> Andre

The horizontal scrollbar option for the wxTextCtrl is not supported by the
PythonCard TextArea component because it is specific to Windows.

From the wxWindows docs:
"wxHSCROLL - A horizontal scrollbar will be created. No effect under GTK+."

If you're only concerned about your program running on Windows then you
could subclass the TextArea component and create your own that supports a
horizontal scrollbar option or override the default TextArea by creating and
appcomponents dir in your application directory, copying the
PythonCardPrototype\components\textarea.py file and then changing the style
attribute in the __init__ method to use wxHSCROLL.

There was a little bit of discussion in the past about having some kind of
raw style attribute for PythonCard components that would allow you to
override the default style parameter and substitute any of those supported
by wxPython, but no work has been done on that. Most of the style parameters
currently used by the components have been chosen to ease cross-platform
coding and provide the most commonly used settings.

As far as horizontal scrolling, I would prefer a toggle method to turn
wrapping on and off. This was added to the wxStyledTextCtrl (wxSTC), so
perhaps you might want to use the CodeEditor component in PythonCard that
wraps wxSTC. It automatically creates a horizontal scrollbar when needed.

ka

The auto-select of the contents of the field is intentional in wxPython,
PythonCard isn't doing anything special. The behavior of the field contents
not being selected when you click into the field is also intentional. This
follows the normal UI guidelines.

I just realized that you are wanting to select all of the text, but by
default wxPython 2.3.3.1 already does this. Are you using an older version
of wxPython?

Personally, I think it is a bit odd to auto-select the contents of a big
field like a TextArea, but seems right for single line text fields. It might
make sense to consider having an option to turn off the auto-select on
gainFocus, but if we did that I would probably want to preserve the previous
selection in the field as well. That would allow us to support behavior in
apps like Outlook that preserve selections as you tab between fields.

As for your code segment, you refer to the component as:

  self.components["TextField"]

when you could have used

  self.components.TextField

In addition, since the event handler is for the TextField component you
don't have to refer to it by name at all and can simply use event.target to
refer to the field the event occurred in. SetSelection also has a special
option

"Selects the text starting at the first position up to (but not including)
the character at the last position. If both parameters are equal to -1 all
text in the control is selected."

So, if you are still using an older wxPython, your event handler can be
simplified to:

    def on_TextField_gainFocus(self, event):
        event.target.SetSelection(-1, -1)

With wxPython 2.3.3.1 you shouldn't need it at all.

ka

> -----Original Message-----
> From: Sergio Campitelli [mailto:pwrsrg@...]
> Sent: Saturday, November 23, 2002 2:49 PM
> To: Kevin Altis
> Subject: Re: Auto select all - when entering a TextField
>
>
> Thank you!
>
> What I was doing wrong was I was using the KeyPress instead of
> the gainFocus
> event. With gainFocus it only occurs once the field is selected
> not as keys
> are being pressed down.
>
> So I keyed it as follows:
>
>     def on_TextField_gainFocus(self, event):
>         txt = self.components["TextField"].text
>         self.components["TextField"].SetSelection( 0, len(txt) )
>
> This works with tab only.  When I mouse click in the field, it puts the
> curser where I click.  It doesn't "highlight" / "autoselect" the entire
> content within the field like 'tab' does.
>
> I think "mouseDown" or "mouseUp" might be doing something after it gains
> focus.
>
> Serg
>
>
> ----- Original Message -----
> From: "Kevin Altis" <altis@...>
> To: "Sergio Campitelli" <pwrsrg@...>; "pythoncard-Users"
> <pythoncard-users@...>
> Sent: Saturday, November 23, 2002 1:18 PM
> Subject: RE: Auto select all - when entering a TextField
>
>
> > Are you saying that with a TextField or TextArea component that as you
> type
> > a character the field contents get selected? Does that happen
> with all the
> > samples such as widgets too or just your program? Can you send
> some code?
> >
> > If something is happening while typing that implies that you've
> created a
> > keyDown, keyUp, or keyPress handler, so maybe something is
> wrong in there.
> > If you need to change the default behavior of a fields contents being
> > selected when the field gets focus from the user pressing the
> Tab key then
> > that could be done in a gainFocus handler.
> >
> > ka
> >
> > > -----Original Message-----
> > > From: Sergio Campitelli
> > > Subject: Auto select all - when entering a TextField
> > >
> > >
> > > I'm not quit sure how to Auto Select ... that is ... when I
> > > tab/point&click
> > > to a field it will select all the contents in that field.
> > > All that has to be done is key new contents ... tab out ... and your
> done
> > > entering.
> > >
> > > I noticed #event.TextEnterEvent has been commented out because I could
> use
> > > event.KeyPressEvent instead so I'm told.
> > >
> > > self.events.extend([event.KeyPressEvent,
> > >                  event.KeyDownEvent,
> > >                  event.KeyUpEvent,
> > >                  #event.TextEnterEvent,
> > >                  event.TextUpdateEvent,
> > >                  event.CloseFieldEvent
> > >          ])
> > >
> > > But I would like to auto select once not continually (that is as
> > > I'm typing
> > > information in the field it continues to select the entire field.)
> > > I must be doing something wrong
> > > Can somebody help me?
> > >
> > > Serg
> >
> >
>
>
>

On Wednesday 20 November 2002 13:55 pm, you wrote:
> I stumbled across PythonCard after experimenting with TK, pyGTK and pyQT.
>
> What are the specific limitations of pythoncard that I wouldn't experience
> working directly with wxPython?
>

As anybody who has read my postings to this list will testify, I'm an 
absolutely rabid advocate of PythonCard, and have been since I discovered it 
at the beginnning of the summer. If you're interested in some of the reasons 
why I like it so much, please see:

http://www.linux2000.com/pythoncard.html
http://www.linux2000.com/pysshed.html
http://www.linux2000.com/pimp.html

The only specific limitation I can think of is that some of the more advanced 
widgets that wxPython offers (tree controls & tabbed dialogs to name but 2) 
aren't fully supported (yet) by the PythonCard framework, but having said 
that, one of the things I *really* like about it is that if you come up 
against a limitation, the framework doesn't prevent you from using native 
wxPython code if you want to.

I'm still very much at the 'newbie' stage as far as wxPython is concerned - I 
found that PythonCard allowed me to take the minimal understanding I already 
have and begin coding useful apps after about 30 minutes of studying the 
walk-throughs. Given that my 5 year old daughter sometimes has a greater 
attention span than I do, this is a very good thing! :-)

-- 

Regards

Phil Edwards
Senior UNIX Systems Administrator
==========================================================================
Mistral Internet Group                              http://www.mistral.net
Tel: +44 (0)1273 747432                           Fax   +44 (0)1273 747452

Running Mandrake Linux release 8.2 (Bluebird) for i586 Kernel 2.4.18-6mdk
System uptime : 34 days,  2:01,  3 users,  load average: 0.42, 0.26, 0.27 
==========================================================================

--- Anthony Barker <abarker@...> wrote:
> What are the specific limitations of pythoncard that I wouldn't
> experience working directly with wxPython?

Although I have been highly impressed with both the design and the
features of Pythoncard (especially the Resource Editor), I have
been unable to find a way to use it for my work because of (what I
perceive as) the following deficiencies:

- no support for wxSizers at present
- no support for wxNotebook (AFAIK)
- minimal or no support for custom widgets or "mega-widgets"
    (related to this, lack of inheritance in creating resources)
- no support for MVC or Document/View architecture

Of course there is no DIRECT support for the last item in wxPython
either. If you want to do MVC or Doc/View in wxPython, you have to
set up the framework yourself, but at least you have that option.

Please understand that these are only my perceptions. If I am
mistaken in this analysis, my apologies. Also, if these are not
features that you require, Pythoncard is an exceptionally easy to
use tool. You may also want to take a look at the ToDo list on the
Pythoncard wiki.


=====
Donnal Walter
Arkansas Children's Hospital

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com

> -----Original Message-----
> From: Anthony Barker
>
> I stumbled across PythonCard after experimenting with TK, pyGTK and pyQT.
>
> What are the specific limitations of pythoncard that I wouldn't experience
> working directly with wxPython?
>
> Thanks
>
> Anthony

Since PythonCard sits on top of wxPython you can always resort to "raw"
wxPython when PythonCard doesn't do something you want. So, if you need
sizers, then you need to code them up and stick them in the openBackground
event handler as many of the samples show.

You can use wxPython controls that aren't wrapped as components, but then
you don't get the automatic event binding, dot notation attributes (.text
instead of GetValue/SetValue methods) and resource file support of the
PythonCard components. The components as subclasses of wxPython controls
support all the wxPython methods and they don't use internal caching of
values, so it is safe to use the raw methods whenever you want.

The event handlers in PythonCard use (self, event) parameters just like
normal wxPython event handlers so again you can mix and match as needed. The
events themselves are just wxPython event objects, but some of the most
commonly used values of each event, such as the event.target attributes are
automatically added to the object when the event occurs so you can use
something like event.target.keyCode instead of
event.GetEventObject().GetKeyCode(). That probably seems like a small point,
but it seems easier to remember and makes code easier to read, or at least
that is what I tell myself. <wink>

When a particular wxPython feature is not yet wrapped for PythonCard, it is
typical to just include the raw wxPython and get the feature working before
deciding whether wrapping would result in simplifying its usage. Timers as
used in the worldclock sample are a good example of this. The timer event
handler is wrapped, so handling a timer is no different than any other
event. However, it is unclear whether there are any advantages to wrapping a
wxTimer object without losing functionality, so those are not yet wrapped
and might not be; for now, you just associate a wxTimer with a component
(components again are subclasses of wxPython controls) and you're set.

PythonCard does provide some additional classes for turtle graphics, a
double-buffered bitmap class (BitmapCanvas), runtime tools, etc. that you
don't get for free just using wxPython. In many cases, any PythonCard sample
or extra functionality classes could be converted back to raw wxPython with
relative ease. Simply think of the PythonCard version as the RAD prototype.
I generally prefer to bang out working examples quickly and then modify the
design and app over time. Most of the PythonCard tools and samples started
out as working apps with coding time anywhere from 15 minutes (codeEditor
tool based on the textEditor sample) to a weekend, but an afternoon is
pretty typical. I was chatting with Patrick on Yahoo at the time and bet him
I could create the CodeEditor component and app in less than 15 minutes so
that one sticks in my mind.

When you need to mix a lot of raw wxPython and PythonCard, chances are you
might be better off just using wxPython. Also, if your wxPython skills are
already good, you might be more comfortable just using wxPython with Boa,
wxDesigner, etc. I would like to have better support for the wxXMLResource
layout format in PythonCard, but one big problem is that there doesn't seem
to be a way of supporting subclasses of controls which is what all the
PythonCard components are (please correct me if I'm wrong). Plus, the
wxXMLResource doesn't have any way of doing post initialization, so setting
of attributes like the font, items, colors wouldn't be supported.

Finally, PythonCard clearly is not at the stage where the API is stable and
well documented, so unless you plan on paying attention to the mailing list
and/or you only need to do something that is a slight variation on an
existing sample, raw wxPython might be better for your longer-term needs.

I definitely have not been working on PythonCard as intensively in the last
few months as I did the previous year. Mostly this is because there is
little developer input except by myself and so I generally only work on the
framework now in response to a bug report, a simple feature request, or
because a sample I'm working on must have a particular feature. The sample
apps that I write are my prime motivator for PythonCard work.

Once the videogame season is over and/or more collaborative development
starts up I'll probably work on it more intensively. [Side note for GameCube
owners, Metroid Prime is great!] There are a number of things such as
rewriting the resourceEditor that are such big projects I have a hard time
getting motivated to work on them.

I think that for simple projects, especially apps you just want to use for
yourself, PythonCard is about as easy as it gets to create GUI apps for
Python. Bigger project needs require that you look elsewhere for now.

ka

Kevin Altis wrote:
> 
> wxDesigner, etc. I would like to have better support for the wxXMLResource
> layout format in PythonCard, but one big problem is that there doesn't seem
> to be a way of supporting subclasses of controls which is what all the
> PythonCard components are (please correct me if I'm wrong). 

Okay, consider yourself corrected. ;-)

2.3.3.1 added support for deriving classes from wxXmlResourceHandler 
that handle creating objects of new class types.  In 2.3.4 there is also 
support for using a subclass attribute in the xml tag, for example

	<object class="wxButton" subclass="myModule.myButton">
	...
	</object>


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!

Excellent, so it sounds like if we made 2.3.4 a minimum for PythonCard, when
2.3.4 becomes available, then we could switch to wxXmlResource as the format
for PythonCard assuming that I can figure out how to read and write the
files for a resourceEditor app. Now we would still need support for post
initialization of certain attributes and we need to make sure that there is
going to be some interop for tools like wxDesigner, but this is better than
the situation when I was ignorant a few hours ago.

The other thing is that then I could subclass wxMenuBar, wxMenu, wxMenuItem
and make sure they have a name attribute just like classes derived from
wxWindow. It looks like the name is already supported in the wxXmlResource,
but the class doesn't use it, so just a small subclass that adds the name
attribute in the __init__ would be needed. Again, good news.

ka

> -----Original Message-----
> From: pythoncard-users-admin@...
> [mailto:pythoncard-users-admin@... Behalf Of Robin
> Dunn
> Sent: Thursday, November 21, 2002 4:25 PM
> To: Kevin Altis; pythoncard-users
> Subject: Re: [Pythoncard-users] limitations of pythoncard
>
>
> Kevin Altis wrote:
> >
> > wxDesigner, etc. I would like to have better support for the
> wxXMLResource
> > layout format in PythonCard, but one big problem is that there
> doesn't seem
> > to be a way of supporting subclasses of controls which is what all the
> > PythonCard components are (please correct me if I'm wrong).
>
> Okay, consider yourself corrected. ;-)
>
> 2.3.3.1 added support for deriving classes from wxXmlResourceHandler
> that handle creating objects of new class types.  In 2.3.4 there is also
> support for using a subclass attribute in the xml tag, for example
>
> 	<object class="wxButton" subclass="myModule.myButton">
> 	...
> 	</object>
>
>
> --
> Robin Dunn
> Software Craftsman
> http://wxPython.org  Java give you jitters?  Relax with wxPython!

> -----Original Message-----
> From: Sergio Campitelli
>
> I'm a newbe as they say.  I hope I'm not over-stepping my boundry
> by saying
> that: closeField event is not working for the component
> 'RightTextfield' but
> is working for 'TextField'.  I'm I doing something wrong?
> By the way, this program is so fast and easy to use ... even
> someone like me
> isn't really having any trouble.
>
> Sid

In PythonCardPrototype\components\righttextfield.py the events list is
missing CloseFieldEvent, so the code block should look like:

        self.events.extend([event.KeyPressEvent,
                event.KeyDownEvent,
                event.KeyUpEvent,
                #event.TextEnterEvent,
                event.TextUpdateEvent,
                event.CloseFieldEvent
        ])

and yes TextEnterEvent is commented out on purpose because you can simply
get that with a keyPress handler.

However, this is not the core of the problem. [Beware, wxPython innards
ahead.] The real issue is that the wxRightTextCtrl has its own
EVT_KILL_FOCUS binding and for some reason calling Skip() doesn't result in
the PythonCard event _dispatch being called. I discussed this with Robin
back in August since it seems like a wxPython bug to me, but the issue
wasn't really resolved. See the wxPython\lib\rightalign.py module for the
wxRightTextCtrl code.

I went ahead and made a fix and checked it into cvs so that the closeField
event would fire, but I don't know how to make the loseFocus event show up
without understanding more of the inner workings of duplicate event handler
bindings. I'll bring this up on wxPython-users to see if a solution can be
found.

ka

Lovely, yet another Windows and Linux difference. The panel should not be
involved in the events. Can someone else on Linux verify that they get this
same exception?

Phil, you said wxPython-2.3.3 below, do you mean 2.3.3.1? I don't know what
the differences are between 2.3.3 and 2.3.3.1, but it would be good to be
accurate about the version numbers before nagging Robin.

In the Message Watcher (-m on the command-line) what you should see is
something like this after creating a button and dragging it around:

mouseDown : Button1
mouseDrag : Button1
...more mouseDrag messages...
mouseDrag : Button1
mouseUp : Button1
mouseClick : Button1


ka

> -----Original Message-----
> From: pythoncard-users-admin@...
> [mailto:pythoncard-users-admin@... Behalf Of Phil
> Edwards
> Sent: Friday, November 15, 2002 5:05 PM
> To: PythonCard Users
> Subject: [Pythoncard-users] resourceEditor throwing an exception
>
>
> My setup:
>
> I happened to be running the resource editor from a command
> prompt tonight,
> and noticed that the exception shown below gets thrown when I try
> to drag a
> Button widget to a new location.
>
> Traceback (most recent call last):
>   File
> "/usr/lib/python2.2/site-packages/PythonCardPrototype/components/b
> utton.py",
> line 131, in _dispatch
>     if binding.wxPython_EventBinding._dispatch(self, aWxEvent):
>   File "/usr/lib/python2.2/site-packages/PythonCardPrototype/binding.py",
> line 205, in _dispatch
>     self._component.notifyEventListeners( evt )
>   File
> "/usr/lib/python2.2/site-packages/PythonCardPrototype/event.py", line
> 334, in notifyEventListeners
>     listener.eventOccurred( event )
>   File
> "/usr/lib/python2.2/site-packages/PythonCardPrototype/dispatch.py",
> line 81, in eventOccurred    handler.getFunction()(self._scriptable,
> nativeEvent)
>   File
> "/home/phile/pycard/tools/resourceEditor/resourceEditor.py", line 323,
> in on_mouseDrag
>     if event.target.name not in self.sizingHandleNames and
> self.components.has_key(self.startName):
> AttributeError: Panel instance has no attribute 'name'
>
> Although I've had a look at the code, I haven't been playing around with
> PyCard for long enough to truly understand what it's doing. It
> looks to my
> untrained eye as though the Panel is receiving the mouse drag
> event instead
> of the button...
>
> A quick run down the components menu reveals that the same
> exception is also
> thrown when trying to drag CheckBox, Choice, Gauge, Image,
> ImageButton, List,
> RadioGroup, StaticBox and StaticLine widgets. All other components can be
> dragged normally.
>
> At the point where the exception occurs, event.__dict__ contains this:
>
> {'y': 4, 'target': <C wxPanel instance at _86602c8_wxPanel_p>, 'x': 47,
> 'this': '_bfffeb30_wxMouseEvent_p', 'position': (47, 4), 'altDown': 0,
> 'thisown': 0, 'controlDown': 0, 'eventObject': <C wxPanel instance at
> _86602c8_wxPanel_p>, 'shiftDown': 0}
>
> And event.target.__dict__ looks like this:
>
> {'_imageFile': '', 'this': '_86602c8_wxPanel_p', 'thisown': 1,
> '_frame': <C
> wxFrame instance at _865f4d0_wxFrame_p>, '_bitmap': None,
> '_backgroundTiling': 0}
>
> Sure enough, there's no 'name' attribute in there. I'm using
> Mandrake Linux
> 8.2, Python-2.2, wxPython-2.3.3 and PythonCard-0.6.9. I've also
> found that I
> can position these components manually by simply keying the
> co-ordinates into
> the 'position' field in the properties list.
>
> --
>
> Regards
>
> Phil Edwards
> Brighton, UK

On Saturday 16 November 2002 2:34 am, Kevin Altis wrote:
> Phil, you said wxPython-2.3.3 below, do you mean 2.3.3.1? I don't know what

Yes, I've installed the wxPythonGTK-py2.2-2.3.3.1-1 RPM from http://www.wxpython.org

>
> In the Message Watcher (-m on the command-line) what you should see is
> something like this after creating a button and dragging it around:
>
> mouseDown : Button1
> mouseDrag : Button1
> ...more mouseDrag messages...
> mouseDrag : Button1
> mouseUp : Button1
> mouseClick : Button1
>

Hmm - no mouseDrag events:

openBackground : bgDrag
openBackground : bgDrag
openBackground : bgTemplate
command : menuComponentAddButton
mouseEnter : bottomRight
mouseLeave : bottomRight
mouseEnter : Button1
mouseDown : Button1
mouseLeave : Button1
mouseLeave : Button1
mouseEnter : Button1
mouseDown : Button1
mouseLeave : Button1
mouseLeave : Button1

--

Regards

Phil Edwards
Brighton, UK

I've checked in changes to samples.py, resourceEditor.py, codeEditor.py and
findfiles.py that hopefully take care of spaces in both the Python
executable and script paths. Please report any problems directly to me
rather than the list and I'll iterate over some variations (if necessary) to
get this issue closed out. The changes impact Linux and Mac OS X, not just
Windows. I did some basic tests and didn't notice any problems, but that
doesn't mean I didn't introduce a quoting bug by mistake.

ka

> -----Original Message-----
> From: pythoncard-users-admin@...
> [mailto:pythoncard-users-admin@... Behalf Of
> Michael Sorich
> Sent: Sunday, November 10, 2002 3:18 PM
> To: pythoncard-users@...
> Subject: RE: [Pythoncard-users] run script path problem
>
>
> I am running version 0.6.9. Furthermore, I am using PythonCard with both
> Python 2.2.2 and 2.1.2 (there does not seem to be any difference between
> the two in terms of this problem).
>
> I ran a few experiments and it is the sys.executable variable that is
> the problem. Furthermore the value of sys.executable does vary depending
> on how you launch the script.
>
> If I run sample.py from the command line, then the value of
> sys.executable is c:\progra~1\python21\python.exe. In this case you can
> launch the example programs.
>
> If I run sample.py from codeEditor the value of sys.executable is
> c:\program files\python21\python.exe. In this case trying to launch the
> examples only results in the following being printed to the prompt:
> C:\program: can't open file 'Files\python21\python.exe'.
>
> The same happens with findfiles.
>
> However, when I run findfiles from the start menu and attempt to open a
> file found, the value of sys.executable is C:\Program
> Files\Python22\pythonw.exe. However, sys.executable is
> C:\PROGRA~1\Python22\python.exe for samples.py when run from the start
> menu. In this case samples.py works, while findfiles.py doesn't.
>
>
> If I use this,
> if ' ' in sys.executable:
> 	os.spawnv(os.P_NOWAIT, sys.executable, ['"'+sys.executable+'"',
> program] + args)
> else:
> 	os.spawnv(os.P_NOWAIT, sys.executable, [sys.executable, program]
> + args)
> samples and findfiles work under all three situations described above.
>
> Hope this helps. Let me know if there is anything else I can do.
>
>
> Michael Sorich
> PhD Student
> School of Pharmaceutical, Molecular and Biomedical Sciences
> University of South Australia
> Email: michael.sorich@...
>            mike_sorich@...
>
>
> -----Original Message-----
> From: Kevin Altis [mailto:altis@...]
> Sent: Saturday, 9 November 2002 5:00 AM
> To: Michael Sorich
> Subject: RE: [Pythoncard-users] run script path problem
>
> Hi Michael,
> if you have time to do a little debugging with me that would be helpful.
> First of all, I want to make sure you are using the PythonCardPrototype
> that
> is in cvs or the version 0.6.9 release.
>
> I'm looking at the samples.py launch code and it looks like it is doing
> the
> same thing as the findfiles launch code, but I'll go ahead and make some
> adjustments. In particular, I'm using sys.executable, which seems to get
> quoted correctly, otherwise neither samples.py or findfiles.py should
> work.
> However, I guess that the problem might instead be the quoting on the
> program with findfiles, so perhaps this change would work:
>
>         log.debug(args)
>         if ' ' in program:
>             program = '"' + program + '"'
>         if sys.platform[:3]=='win':
>             os.spawnv(os.P_NOWAIT, sys.executable, [sys.executable,
> program]
> + args)
>
> I deleted the commented lines for brevity here. The only new code is the
> if
> ' ' to add quotes. I'm going to update the samples.py code in the same
> way:
>
>         if ' ' in filename:
>             filename = '"' + filename + '"'
>         if sys.platform[:3]=='win':
>             os.spawnv(os.P_NOWAIT, sys.executable, [sys.executable,
> filename] + args)
>
> If this works we can move onto the resourceEditor and codeEditor.
>
> ka
>
> > -----Original Message-----
> > From: pythoncard-users-admin@...
> > [mailto:pythoncard-users-admin@... Behalf Of
> > Michael Sorich
> > Sent: Thursday, November 07, 2002 9:17 PM
> > To: pythoncard-users@...
> > Subject: RE: [Pythoncard-users] run script path problem
> >
> >
> > I am running Windows XP. Findfiles and resourceEditor do not work
> > without adjustment, however samples launcher seems to.
> >
> > Michael
> >
> >
> > -----Original Message-----
> > From: pythoncard-users-admin@...
> > [mailto:pythoncard-users-admin@...] On Behalf Of
> Kevin
> > Altis
> > Sent: Friday, 8 November 2002 11:48 AM
> > To: Michael Sorich; pythoncard-users@...
> > Subject: RE: [Pythoncard-users] run script path problem
> >
> > Which version of Windows are you using? I thought we solved this
> > problem,
> > but I guess I dropped the ball. You'll have similar issues with
> > findfiles,
> > the samples launcher, and the resourceEditor.
> >
> > ka
> >
> > > -----Original Message-----
> > > From: pythoncard-users-admin@...
> > > [mailto:pythoncard-users-admin@... Behalf Of
> > > Michael Sorich
> > > Sent: Thursday, November 07, 2002 3:32 PM
> > > To: pythoncard-users@...
> > > Subject: [Pythoncard-users] run script path problem
> > >
> > >
> > > Hi,
> > >
> > > I have just started to use PythonCard. Just thought you may want to
> > know
> > > about a bug/problem I may have found.
> > >
> > > My python path is c:\program files\python22 and when I tried to run
> > > scripts from the editors (eg CodeEditor) they would not work,
> because
> > > there was a space in the path.
> > >
> > > In the runScript function of the editor files, if I change
> > > os.spawnv(os.P_NOWAIT, python, [python, '-i', filename] + args)
> > > to
> > > os.spawnv(os.P_NOWAIT, python, ['"'+python+'"', '-i', filename] +
> > args)
> > > the scripts run (eg line 1017 in CodeEditor.py)
> > >
> > > Let me know if there is a better way to fix this.
> > >
> > > Cheers
> > >
> > > Michael Sorich

On Sunday 10 November 2002 06:53 pm, Kevin Altis wrote:
> I've checked in changes to samples.py, resourceEditor.py,
> codeEditor.py and findfiles.py that hopefully take care of spaces in
> both the Python executable and script paths. Please report any
> problems directly to me rather than the list and I'll iterate over
> some variations (if necessary) to get this issue closed out. The
> changes impact Linux and Mac OS X, not just Windows. I did some basic
> tests and didn't notice any problems, but that doesn't mean I didn't
> introduce a quoting bug by mistake.

The codeEditor still works for me under KDE on Linux, even with a 
directory containing a space. Just FYI.

-- 
Patrick K. O'Brien
Orbtech      http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------