Menu
▾
▴
pythoncard-users
|
From: Simon H. <Sim...@ma...> - 2005-01-06 13:10:16
|
I'm getting a similar problem to Dan. The Windows installer bombed out about 80% of the way through. However Pythoncard does seem to be installed and the sample apps seem to work ok. However I've been workig through the first two tutorials, and neither work. The sample apps aren't as described. The function you're told to modify in the first tutorial isn't in the script, and I've modified the Minimal app as described in the second tutorial (the Counter app) but it doesn't work. Yet as I said, the sample apps all seem to run ok, very odd. Simon _____________________________ Simon Hibbs Senior Support Engineer (Marconi) |
|
From: Andy T. <an...@ha...> - 2005-01-24 08:23:59
|
Simon,
There are a number of issues here, I'll try to deal with them in turn;
Simon Hibbs wrote:
> I'm getting a similar problem to Dan. The Windows
> installer bombed out about 80% of the way through.
The .exe installer was built with Python 2.3 and this may be why it
bombs out when installing with version 2.4. According to my not very
extensive testing the error occurs when we try and create the start menu
program group and icons. As far as I can tell PythonCard installs properly.
It's not very good though. For the next release we probably need to
build two versions of the .exe, one for Python 2.3 and another for
Python 2.4. If anyone would like to investigate and explain why this is
a problem it would be more than welcome.
>
> However Pythoncard does seem to be installed and the
> sample apps seem to work ok.
>
Yup, you just probably won't have a 'PythonCard' program group in your
start menu.
> However I've been workig through the first two tutorials,
> and neither work. The sample apps aren't as described.
Err, correct. The documentation and supporting materials are a bit out
of date. Sorry.
>
> The function you're told to modify in the first tutorial isn't
> in the script, and I've modified the Minimal app as described
> in the second tutorial (the Counter app) but it doesn't work.
I'll update the first tutorial and sample script a.s.a.p.
I ran through the second tutorial and everything *seemed* to work (under
both Python 2.3 and 2.4). Can you give a bit more detail, did the
scripts for both of the buttons not work? What happens when you put some
simple print statements in the methods? For instance, try adding a line
to the provided incrBtn method, changing it from;
def on_incrBtn_mouseClick(self, event):
startValue = int(self.components.field1.text)
endValue = startValue + 1
self.components.field1.text = str(endValue)
To
def on_incrBtn_mouseClick(self, event):
print "I am in the incrBtn handler"
startValue = int(self.components.field1.text)
endValue = startValue + 1
self.components.field1.text = str(endValue)
And then running your application from the command line. Report any
errors, warnings or output to the command line that you see.
>
> Yet as I said, the sample apps all seem to run ok, very
> odd.
>
> Simon
> _____________________________
> Simon Hibbs
> Senior Support Engineer (Marconi)
>
Indeed they do for me too. But if you find any more problems please
report them to the list.
Regards,
Andy
--
--------------------------------------------------------------------------------
From the desk of Andrew J Todd esq - http://www.halfcooked.com/
|
|
From: Andy T. <an...@ha...> - 2005-02-09 08:25:50
|
Andy Todd wrote: > Simon, > > There are a number of issues here, I'll try to deal with them in turn; > > Simon Hibbs wrote: > >> I'm getting a similar problem to Dan. The Windows >> installer bombed out about 80% of the way through. > > > The .exe installer was built with Python 2.3 and this may be why it > bombs out when installing with version 2.4. According to my not very > extensive testing the error occurs when we try and create the start menu > program group and icons. As far as I can tell PythonCard installs properly. > > It's not very good though. For the next release we probably need to > build two versions of the .exe, one for Python 2.3 and another for > Python 2.4. If anyone would like to investigate and explain why this is > a problem it would be more than welcome. > >> >> However Pythoncard does seem to be installed and the >> sample apps seem to work ok. >> > > Yup, you just probably won't have a 'PythonCard' program group in your > start menu. > >> However I've been workig through the first two tutorials, >> and neither work. The sample apps aren't as described. > > > Err, correct. The documentation and supporting materials are a bit out > of date. Sorry. > >> >> The function you're told to modify in the first tutorial isn't >> in the script, and I've modified the Minimal app as described >> in the second tutorial (the Counter app) but it doesn't work. > > > I'll update the first tutorial and sample script a.s.a.p. > [snip] I've updated the sample application and walkthrough documentation. These are in CVS now for anyone who wants to verify my changes and will appear in the next release. As an aside, I had to change the event handler because on_menuFileExit_select doesn't seem to work on OSX. I suspect it's something to do with the way wxWidgets binds to the native menus. For starters the menu option appears as 'Quit' rather than 'Exit'. The message watcher doesn't show any events when the exit option is selected either. I added an 'About' menu item and the handler is invoked when this is selected, as expected. I noticed that I get a free 'help' menu on OSX as well, which I don't seem to be able to add items to with the resource file. I'm presuming this is known behaviour with wx, but would appreciate someone else confirming it for me. I can't verify if this behaviour is platform specific as my Windows/Linux machine currently has a rather poorly screen. Can someone please run the 'starter1' application in the docs/GettingStarted folder from CVS and let me know if the FileExit event handler is working or not, and whether a 'help' menu is created. Thanks in advance, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2005-02-16 08:42:54
|
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1D1Klq-0001vp-Mo for pyt...@li...; Wed, 16 Feb 2005 00:42:54 -0800 Received: from ptb-relay01.plus.net ([212.159.14.212]) by sc8-sf-mx2.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.41) id 1D1Klp-0007dw-1e for pyt...@li...; Wed, 16 Feb 2005 00:42:54 -0800 Received: from [80.229.32.187] (helo=[10.0.0.4]) by ptb-relay01.plus.net with esmtp (Exim) id 1D1Klf-000Edh-2s for pyt...@li...; Wed, 16 Feb 2005 08:42:44 +0000 From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX To: "Pythoncard Users" <pyt...@li...> Subject: Re: [Pythoncard-users] Install problem with python 2.4 Message-Id: <200...@re...> In-Reply-To: <420...@ha...> References: <420...@ha...> X-Mailer: CTM PowerMail 4.2.1 us Carbon <http://www.ctmdev.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 Sender: pyt...@li... Errors-To: pyt...@li... X-BeenThere: pyt...@li... X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/pythoncard-users>, <mailto:pyt...@li...?subject=unsubscribe> List-Id: <pythoncard-users.lists.sourceforge.net> List-Post: <mailto:pyt...@li...> List-Help: <mailto:pyt...@li...?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/pythoncard-users>, <mailto:pyt...@li...?subject=subscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=pythoncard-users> Date: Wed Feb 16 00:43:18 2005 X-Original-Date: Wed, 16 Feb 2005 08:46:17 +0000 |
|
From: Andy T. <an...@ha...> - 2005-02-19 00:16:16
|
XXXXXXXXXXX wrote:
> On Wed, 9 Feb 2005 19:25:15 +1100, Andy Todd wrote:
>
>
>>As an aside, I had to change the event handler because
>>on_menuFileExit_select doesn't seem to work on OSX. I suspect it's
>>something to do with the way wxWidgets binds to the native menus.
>>
>>For starters the menu option appears as 'Quit' rather than 'Exit'. The
>>message watcher doesn't show any events when the exit option is selected
>>either.
>>
>>I added an 'About' menu item and the handler is invoked when this is
>>selected, as expected. I noticed that I get a free 'help' menu on OSX as
>>well, which I don't seem to be able to add items to with the resource file.
>>
>>I'm presuming this is known behaviour with wx, but would appreciate
>>someone else confirming it for me.
>
>
> Sorry Andy, were you just asking for somebody with Python 2.4 to test
> this? I'm still on Python 2.3.x/PythonCard 0.81/OSX Panther and the usual:
>
> def on_menuFileExit_select(self, event):
> self.Close()
>
> works fine. With the resource editor I can add a 'help' menu with an
> 'about' item and it replaces the system-wide help menu.
>
> Neil
>
Indeed, it appears I had a subtle bug in my help menu, serves me right
for adding it manually rather than through the resource editor.
However, the FileExit_select problem is real. Try adding a line to your
method above self.Close() which does something. Anything really. I tried ;
print "Exiting application ..."
and saw no output on the command line. Trying a variety of other things
and none of them got executed. Which leads me to believe that the
binding isn't quite right on Mac OSX. I still haven't been able to
verify if this is a problem on other platforms but will try and have a
go this weekend.
Regards,
Andy
--
--------------------------------------------------------------------------------
From the desk of Andrew J Todd esq - http://www.halfcooked.com/
|
|
From: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - 2005-02-20 18:53:37
|
On Sat, 19 Feb 2005 11:15:49 +1100, Andy Todd wrote: >However, the FileExit_select problem is real. Try adding a line to your >method above self.Close() which does something. Anything really. I tried ; > print "Exiting application ..." > >and saw no output on the command line. Trying a variety of other things >and none of them got executed. Which leads me to believe that the >binding isn't quite right on Mac OSX. I still haven't been able to >verify if this is a problem on other platforms but will try and have a >go this weekend. Ah! You're right....I added the print statement and it never got called. I just tried it on Windows XP, Python 2.3.4, PythonCard 0.81 - same result. Neil |
|
From: Andy T. <an...@ha...> - 2005-02-21 06:27:10
|
XXXXXXXXXXX wrote: > On Sat, 19 Feb 2005 11:15:49 +1100, Andy Todd wrote: > > >>However, the FileExit_select problem is real. Try adding a line to your >>method above self.Close() which does something. Anything really. I tried ; >> print "Exiting application ..." >> >>and saw no output on the command line. Trying a variety of other things >>and none of them got executed. Which leads me to believe that the >>binding isn't quite right on Mac OSX. I still haven't been able to >>verify if this is a problem on other platforms but will try and have a >>go this weekend. > > > Ah! You're right....I added the print statement and it never got called. > > I just tried it on Windows XP, Python 2.3.4, PythonCard 0.81 - same result. > > Neil > I get the same behaviour on my Linux box, so this is definitely a bug. I'll try and see what I can find in the wx documentation and mailing list. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
|
From: Andy T. <an...@ha...> - 2005-02-24 07:44:30
|
Peter C. Norton wrote: > Andy, > > Are you the maintainer of pythoncard? I'm asking because I'm > interested in getting the installation with python2.4 and windows > working. Do you have any ideas about this? > > Thanks, > > -Peter > > On Wed, Feb 09, 2005 at 07:25:15PM +1100, Andy Todd wrote: > [snip] > Peter, I'm not *the* maintainer, although I do have CVS commit privileges. PythonCard is an open source project so anyone can contribute code, documentation, or sample applications. Providing your contribution doesn't break anything it is likely to be accepted into PythonCard. I'm currently (very slowly) looking at some of the issues that have come up in this thread but haven't begun to address the installation 'features' that occur with the binary package of PythonCard under Python 2.4 on Windows - mainly because I don't have a development machine running Windows. As previously stated installing the source distribution doesn't (as far as I know) have any problems and this is the recommended work around for now. I suspect to stop the post installation errors that people are seeing all we need to do is build a binary distribution using Python 2.4 (as well as Python 2.3) for the next release. Ideally I would like to have some independent verification that this is the case and that no other action needs to be taken. To that end I am happy to provide help and advice to anyone else who wants to investigate this further this before I get round to it - which may be some time. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X