pythoncard-users Mailing List for PythonCard (Page 12)

The newly released wxPython 2.8.9.1 fixes the problem with CodeEditor.

On 14/08/2008 20:38, Robin Dunn wrote:
>>> Alexei Vinidiktov wrote:
>>>> I've installed the latest version of wxPython (2.8.8.1) and now Boa
>>>> Constructor won't start. I'm on Windows XP SP2 and Python 2.5.2.
>>>> Here's the traceback I get:
>> [snip]
>>>> File "C:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\_misc.py", line 3313
>>>> , in __init__
>>>> _misc_.FileConfig_swiginit(self,_misc_.new_FileConfig(*args, **kwargs))
>>>> wx._core.PyNoAppError: The wx.App object must be created first!
> 
> It is caused by a change in wxPython. 2.8.8.1 added a check to the 
> config classes to ensure that the app object had been created first in 
> order to correct a crashing bug, but that was a bit of overkill since it 
> didn't really need it in all situations. 2.8.8.2 will relax the 
> restriction to a more appropriate level.
This seems to have been fixed now in the latest release. I upgraded from 
 2.8.0.1 (if it ain't broke...) to 2.8.8.1, to verify that I could see 
the error....and I could. I then upgraded to the new 2.8.9.0 release and 
I was able to start both the code and resource editors. I haven't done 
much beyond that though.
Windows XP + Python 2.5 + wxPython 2.8.9.0 (ansi) + PythonCard 0.8.2.
-- 
XXXXXXXXXXX

Neil Hughes wrote:
> On 15/09/2008 16:10, Rafe wrote:
>>
>> When I install:
>> python 2.5.2
>> wxpython 2.8.8.1
>> pythoncard 0.8.2
>> on my windows xp box, codeEditor does not work. It looks like it 
>> can't find all the wxpython modules, but I am too new at this to know 
>> for sure. 
>
> What error message are you seeing, exactly?
>
It looks like a bug in wxpython 2.8.8.1 So, I'll wait for 2.8.8.2.
Thanks
Rafe

Sorry if this has been asked already. I am having trouble finding list 
archives.
When I install:
 python 2.5.2
 wxpython 2.8.8.1
 pythoncard 0.8.2
on my windows xp box, codeEditor does not work. It looks like it can't 
find all the wxpython modules, but I am too new at this to know for sure. 
I can use a linux box for now, but would like to get everything running 
in windows also.
Rafe

I notice the note from Hugh Kernohan of 2007年11月03日; was there no 
interest in pursuing it? I've pulled the zip file off of 'tweedly.org'. 
Is there any successor file set?
Also, given the level of activity on this project since the last 2006 
update, should I assume that folks consider this project completed? 
Will there be no version 1.0, and this is another project that never 
progresses past a beta release? Actually, the code looks pretty 
polished for beta.
Thanks.

Just curious, but has anyone got it to work?
The discussion seems to have ended here ... although I note that Alex 
(someone) seems to have later added a line for version 2.5 in the 
util.py that came with my version of 0.82 as well ...
http://article.gmane.org/gmane.comp.python.pythoncard.devel/144/ 
match=py2app
 fwiw I have no (apparent) path problems with py2app (unless I force 
one), in that it happily builds my program for me ... when I try to 
run it, though, I get the following:
"An unexpected error has occurred during execution of the main script
TypeError: coercing to Unicode: need string or buffer, NoneType found"
Tracing back as best I can leads me to model.py as well, but 
ultimately to the init of class Application, which is the only place 
that I can guess a NoneType is entering my program:
def __init__(self, frameClass, aFileName=None, rsrc=None)
Still don't understand all this, but if anyone who does is still is 
interested, I'll gladly provide console logs, code, or whatever ...
Cheers,
TM

On 05/06/2008 19:54, XXXXXXXXXXX wrote:
> On 05/06/2008 15:19, Alec Bennett wrote:
>> I'm working on a PythonCard project and can't figure out if it's 
>> possible to set a wx.TE_PROCESS_ENTER style on a textfield. In other 
>> words, I'd like to be able to trigger an event (for example a submit 
>> button type event) when the user presses the enter key while they're in 
>> a text field.
>>
>> Is this possible with PythonCard?
> 
> On some of my windows I have a username text field and password text 
> field, but I want the return/enter key to act the same as the login 
> button next to them, so I use this:
> 
> def on_keyDown(self, event):
> if(event.keyCode == wx.WXK_RETURN):
> if(self.components.LoginButton.enabled == True):
> self.on_LoginButton_mouseClick(event)
> 
> on_keyDown() is catching keyboard events not trapped by any specific 
> widget, but you should be able to use
> 
> on_<text field name>_keyDown()
> 
> to only listen to the specific text field widget you want.
I've just had to do something similar with a password field, i.e. I 
needed the operator to type in the password and then when he/she hits 
return the login button needs to activate. My solution above didn't work 
straight away with text/password fields because, as initially pointed 
out, the return key is not trapped and you have to use the special flag.
Question....I ended up setting the flag in on_initialize() with a line 
at the end that just does:
self.components.PasswordField.WindowStyle |= wx.TE_PROCESS_ENTER
meanwhile I have this method activating the login button when the 
password field gets a return key and there's something typed in:
def on_PasswordField_keyDown(self, event):
 if((event.keyCode == wx.WXK_RETURN) and 
(self.components.PasswordField.text <> '')):
 self.on_LoginButton_mouseClick(event)
 else:
 event.skip()
Is this the best/safest way...or is there something a bit tidier that 
avoids delving into using the underlying wx stuff? It's almost like I 
need a 'special flags' field in the resource editor, but with some 
smarts as to which flags apply to which widget types.
-- 
XXXXXXXXXXX

On 12/08/2008 19:58, Caonabo Taino wrote:
> I installed the latest version of Python card, Python and wxPython.
> when I click the code editor from the start menu nothing happen.
> if I try to click the program from th code editor folder the same thing 
> happen. the find files, resources and layout editor are working.
> the code editor and the tab editor are not working,
Are you running wxPython version 2.8.8.1? It sounds like you might have 
hit the same issue reported by Jim.
-- 
XXXXXXXXXXX

Jim Hill wrote:
>> Alexei Vinidiktov wrote:
> 
>>> I've installed the latest version of wxPython (2.8.8.1) and now Boa
>>> Constructor won't start. I'm on Windows XP SP2 and Python 2.5.2.
>>> Here's the traceback I get:
> [snip]
>>> File "C:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\_misc.py", line 3313
>>> , in __init__
>>> _misc_.FileConfig_swiginit(self,_misc_.new_FileConfig(*args, **kwargs))
>>> wx._core.PyNoAppError: The wx.App object must be created first!
> 
> Werner F. Bruhin wrote:
> > Posted a work around here:
> > https://sourceforge.net/forum/message.php?msg_id=5133566
> 
> 
> My PythonCard codeEditor gets the same error from
> line 3313 in ...\wx\_misc.py
> (Same system and apps as Alexei.)
> 
> I thought it may be a problem in wxPython 2.8.8.1, rather than 
> in Boa or PythonCard, but googling found nothing about it.
It is caused by a change in wxPython. 2.8.8.1 added a check to the 
config classes to ensure that the app object had been created first in 
order to correct a crashing bug, but that was a bit of overkill since it 
didn't really need it in all situations. 2.8.8.2 will relax the 
restriction to a more appropriate level.
-- 
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
 <title></title>
</head>
<body bgcolor="#cccccc" text="#000000">
<p>Hi<br>
</p>
<p>When I try to run PythonCard codeEditor this happens:</p>
<p>Traceback (most recent call last):<br>
 File "codeEditor.py", line 24, in &lt;module&gt;<br>
  from modules import colorizer<br>
 File
"E:\Python\Lib\site-packages\PythonCard\tools\codeEditor\modules\colorizer.py",
line 19, in &lt;module&gt;<br>
  cfg =
STCStyleEditor.initFromConfig(configuration.getStyleConfigPath(),
'python')<br>
 File "E:\Python\lib\site-packages\PythonCard\<font color="#cc0000">STCStyleEditor</font>.py",
line
1224, in <font color="#cc0000">initFromConfig</font><br>
  cfg = <font color="#cc0000">wx.FileConfig</font>(localFilename=configFile,
style=wx.CONFIG_USE_LOCAL_FILE)<br>
 File "E:\Python\lib\site-packages\wx-2.8-msw-unicode\wx\<font
 color="#cc0000">_misc.py</font>",
line <font color="#cc0000">3313</font>, in __init__<br>
  _misc_.<font color="#cc0000">FileConfig_swiginit</font>(self,_misc_.new_FileConfig(*args,
**kwargs))<br>
wx._core.PyNoAppError: The wx.App object must be created first!<br>
</p>
<p>Something similar happens in Boa:</p>
<p></p>
<blockquote type="cite">Werner F. Bruhin wrote:<br>
&gt; Posted a work around here:<br>
&gt; <a class="moz-txt-link-freetext"
 href="https://sourceforge.net/forum/message.php?msg_id=5133566">https://sourceforge.net/forum/message.php?msg_id=5133566</a></blockquote>
<p>But the PythonCard code looks so different <br>
that i don't think Werner's
workaround would help.<br>
cfg is referenced a few times, so you can't just comment it out.<br>
</p>
<p>Did something change in wxPython between 2880 and 2881, <br>
or would this be
caused by any upgrade of wxPython version? <br>
</p>
<p>--<br>
jim<br>
</p>
<p> </p>
</body>
</html>

I installed the latest version of Python card, Python and wxPython.
when I click the code editor from the start menu nothing happen.
if I try to click the program from th code editor folder the same thing
happen. the find files, resources and layout editor are working.
the code editor and the tab editor are not working,
Thank You for any help,
-- 
-----
Fight back spam! Download the Blue Frog.
http://www.bluesecurity.com/register/s?user=Y2FvbmFib3Q3NjEy

jac...@gm...
-- 
Jacob Steele
Alston Contractors, Inc.
827 Vieux Marche'
Biloxi, MS 39530
Phone:(228)-432-2020
Fax: (228)-432-2024

On 2006年03月12日, Fredrik Lundh wrote:
 > it sure looks as if Python's picking up some _imaging.pyd 
file > that doesn't match the Python interpreter you're using.
 >
 > have you verified that you don't have some old _imaging file
 > lying around somewhere ?
I just ran into this problem when first using PythonCard,
and would like to put this solution on record:
The new version of _imaging.pyd is in
x:\Python\Lib\site-packages\PIL
but in
x:\Python\DLLs
I found older versions of both _imaging.pyd and _imagingft.pyd, 
dated 2004年12月10日.
removing these solved the problem.
-- jim

On 05/06/2008 15:19, Alec Bennett wrote:
> I'm working on a PythonCard project and can't figure out if it's 
> possible to set a wx.TE_PROCESS_ENTER style on a textfield. In other 
> words, I'd like to be able to trigger an event (for example a submit 
> button type event) when the user presses the enter key while they're in 
> a text field.
> 
> Is this possible with PythonCard?
On some of my windows I have a username text field and password text 
field, but I want the return/enter key to act the same as the login 
button next to them, so I use this:
 def on_keyDown(self, event):
 if(event.keyCode == wx.WXK_RETURN):
 if(self.components.LoginButton.enabled == True):
 self.on_LoginButton_mouseClick(event)
on_keyDown() is catching keyboard events not trapped by any specific 
widget, but you should be able to use
on_<text field name>_keyDown()
to only listen to the specific text field widget you want.
-- 
XXXXXXXXXXX

I'm working on a PythonCard project and can't figure out if it's possible to
set a wx.TE_PROCESS_ENTER style on a textfield. In other words, I'd like to
be able to trigger an event (for example a submit button type event) when
the user presses the enter key while they're in a text field.
Is this possible with PythonCard?
Thanks for any help.

Christopher Lees wrote:
> Hi all,
> 
> I've been using Pythoncard for a couple of years now. I had a look at
> the Sourceforge site but there doesn't seem to be any developments for
> the past couple of years. The Pythoncard Todo list on wxpython.org does
> seem to have been updated in March of this year.
> 
> Is there any development still going on for Pythoncard, or is the
> framework completely unmaintained?
> 
> Chris Lees
> 
There isn't a lot of development going on at the moment. That's not to 
say that if anyone wishes to provide patches or enhancements to the code 
base they won't be welcome.
And given sufficient commitment CVS access can be arranged.
Regards,
Andy
-- 
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

Hi all,
I've been using Pythoncard for a couple of years now. I had a look at
the Sourceforge site but there doesn't seem to be any developments for
the past couple of years. The Pythoncard Todo list on wxpython.org does
seem to have been updated in March of this year.
Is there any development still going on for Pythoncard, or is the
framework completely unmaintained?
Chris Lees

Aaron Stevens wrote:
> No dice, I fear. I made this change, and still the panel size stays 
> fixed. Unusual, it is.
> 
> Here's a screen shot AFTER I applied that suggested fix....
Is that screen shot cut off around the edges, or did it actually make
the OS X Window frame look cut off? If so, that must be the wrong panel.
Unfortunately, when I looked into the problem on my old G3 running 10.4
w/ Python 2.5(.?) & wxWidgets (?), I don't have the problem, so it's
difficult for me to try and offer any other suggestions right now.
I'll check the versions I've got against what Terry reported earlier and
see if I can't get it to be broken on my machine. If I can, I'll dig
around and see what I can find.
--
John McCormick

On 2008年5月18日, Jason Harthun wrote:
> Hi. I need some help with the Grid component.
>
> Here is the code that I'm working with:
>
> # ...
> def on_grdDataGrid_selectCell(self, event):
> self.components.grdDataGrid.EnableEditing(False)
> event.skip()
>
> def on_grdDataGrid_keyDown(self, event):
> self.components.grdDataGrid.EnableEditing(False)
> event.skip()
> # ...
> def on_grdDataGrid_editorHidden(self, event):
> result = dialog.messageDialog(self, "Are you sure you wish to save the changes?","Save", wx.YES_NO)
> if not result.accepted:
> event.Veto()
> return
> event.skip()
>
>
> I would like to allow editing only if the user double clicks in the 
> cell. After editing a cell and using enter or tab to exit the cell, the 
> dialog associated with the editorHidden event pops up twice. I only 
> want it to pop up once. Any help would be appreciated. Thanks.
IIRC there is a debugger for this, but my guess is that when the new cell 
is entered, it receives one of the cell selection events, while the old 
cell also gets a key down event. Possible solution: check if the editing 
was already disabled before making the EnableEditing call. Possible design 
enhancement: make an editing_enabled property for the grid instead (such 
that the setter only makes the state-change - implicitly triggering the 
event - when the set state is not the existing state).
Karl Knechtel {:>

Hi. I need some help with the Grid component. 
 
 Here is the code that I'm working with:
 
 self.components.grdDataGrid.EnableEditing(False)
 
 def on_grdDataGrid_mouseDoubleClick(self, event):
 self.components.grdDataGrid.EnableEditing(True)
 event.skip()
 
 def on_grdDataGrid_selectCell(self, event):
 self.components.grdDataGrid.EnableEditing(False)
 event.skip()
 
 def on_grdDataGrid_keyDown(self, event):
 self.components.grdDataGrid.EnableEditing(False)
 event.skip()
 
 def on_grdDataGrid_editorShown(self, event):
 result = dialog.messageDialog(self, "Are you sure you wish to edit this cell?","Edit", wx.YES_NO)
 if not result.accepted:
 event.Veto() 
 self.components.grdDataGrid.EnableEditing(False)
 return
 event.skip()
 
 def on_grdDataGrid_editorHidden(self, event):
 result = dialog.messageDialog(self, "Are you sure you wish to save the changes?","Save", wx.YES_NO)
 if not result.accepted:
 event.Veto()
 return
 event.skip()
 
 I would like to allow editing only if the user double clicks in the cell. After editing a cell and using enter or tab to exit the cell, the dialog associated with the editorHidden event pops up twice. I only want it to pop up once. Any help would be appreciated. Thanks.
 
 Jason
 

No dice, I fear. I made this change, and still the panel size stays 
fixed. Unusual, it is.
Here's a screen shot AFTER I applied that suggested fix....

It's got to be that the wxFrame (panel) that hosts the controls no 
longer sizes appropriately on Mac. I don't have PythonCard running on a 
Mac at present, but I have a theory that adding:
 self.panel.size = self.size
to resourceEditor.py at line 1292 or so, assuming everyone else has the 
same resourceEditor I do, would correct it, albeit in a 
less-than-perfect way since it doesn't take into account the menu bar, 
status bar,etc.
I really don't know what I'm doing here, but I was surprised not to see 
any sizers or equivalent code for self.panel in resourceEditor.py, since 
(I assume) wx.Panel doesn't grow to fill its parent by default. Maybe it 
does on Windows and doesn't on Mac, and that's the problem?
Anyway, I'll try and get PythonCard up and running on my Mac and see if 
it helps, or any of you Mac guys are welcome to try it and let me know.
--
John McCormick

Alec Bennett wrote:
> 
> In wx I could set something like 
> self.SetBackgroundStyle(wx.BG_STYLE_CUSTOM), but not in PythonCard as 
> far as I can tell?
> 
Hi Alec:
You should still be able to do all the regular 'raw' wxPython stuff in 
your PythonCard application, since most of the PythonCard objects are 
subclassed from their wxPython equivalents.
As an example, I have the following code in a little applet I wrote to 
simplify the management of profiles for the various wireless networks I 
use regularly:
 def on_scanBtn_mouseClick(self, event):
 win = MyMiniFrame(self, "Wireless Network Scan",
 style=wx.DEFAULT_FRAME_STYLE | 					 
wx.TINY_CAPTION_HORIZ)
 win.SetSize((200, 60))
 win.CenterOnParent(wx.BOTH)
 win.Show(True)
 win.Update()
 win.Refresh()
 wx.Yield()
This is just some raw wxPython code called from in the middle of the 
PythonCard app that surrouonds it.
-- 
Regards
Phil Edwards | PGP/GnuPG Key Id
Brighton, UK | 0x68393AEE

I have a PythonCard app that creates collages from a directory of pictures.
It makes a show of the process, displaying each picture as its added, about
two per second, full screen.
My problem is that every time a new picture is added, the whole screen
flickers. This isn't really that surprising consdiering the way I'm doing
it: the new image gets pasted onto a fresh canvas and then the old image
(the previous frame) gets swapped out for the new image (the current frame).
When this image swap happens the screen flickers a little bit, but since it
happens twice per second its very distracting.
Can anyone think of a way to reduce this flicker?
In wx I could set something like
self.SetBackgroundStyle(wx.BG_STYLE_CUSTOM), but not in PythonCard as far as
I can tell?
Or some other way to do this?
Thanks for any tips.

There seems to be a workaround: changing the template that is opened by
default when the layoutEditor is opened:
If you modify tools/resourceEditor/templates/templates.rsrc as follows
...
 { 'type':'Background',
 'name':'bgTemplate',
 'title':'Standard Template with File->Exit menu',
 'size':( 800, 600 ),
 'style':['resizeable'],
 'statusBar':0,
...
the panel that can be worked with is 800 x 600 pixels big. Not very elegant,
but this makes the editor at least usable on the Mac. Better would be a
solution that adapts the panel to the size of the window automatically.
2008年5月4日 Christian Boulanger <c.b...@qx...>:
> Hello,
>
> has anybody found out more about this problem? I have the exact same
> issue, which renders the layoutEditor useless on the Mac:
>
>
> http://www.qxtransformer.org/screenshots/pythoncard-mac-leopard-problem.png
>
> Thanks for any information!
>
> Christian
>
> Terry Maloney <terrymaloney <at> globetrotter.net> writes:
>
> >
> > Neil Hughes wrote:
> >
> > > With the following versions the layout looks the same as XP, i.e. all
> > > components are visible and the text area fills the frame:
> > >
> > > OSX 10.4.11 (PowerPC)
> > > Python 2.3.5 (as shipped with Tiger)
> > > wxPython 2.5.3.1
> > > PythonCard 0.8.2
> > >
> > > So it looks more like something specific to newer versions of the
> > > OS/wxPython than a platform difference.
> >
> > I'm also using OSX 10.4.11 (PowerPC), so it's probably not the OS,
> > but definitely is related to wxPython ... versions up to 2.7.2.0 work
> > perfectly, 2.8.0.1 introduces the problem. Unfortunately that's
> > probably not going to help Aaron, as 2.7.2.0 doesn't appear to
> > support OSX 10.5.
> >
> >
> -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> >
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> >
>
>
>