pythoncard-users — PythonCard Users and Developers

Re: [Pythoncard-users] layout and font problems on Windows

[Ronny De W. <ron...@gm...>]

This seems to be a PythonCard problem on my Windows configuration,
some more examples:

http://www.5consulting.com/img/tmp/screen1.jpg
resourceEditor Property Editor:
- incomplete button at the right bottom

PythonCard Samples:
custdb: http://www.5consulting.com/img/tmp/screen2.jpg
- overlapping fields

dbBrowser: http://www.5consulting.com/img/tmp/screen3.jpg
- database text field only half visible

minimalList: http://www.5consulting.com/img/tmp/screen4.jpg
- horizontal scrollbar shouldn't be there ?

moderator: http://www.5consulting.com/img/tmp/screen5.jpg
- fonts look too big, ie. "Time Left:" does not fit

mp3player: http://www.5consulting.com/img/tmp/screen6.jpg
- buttons disappear at bottom of the window

I also looked at the wxPython samples and they look ok.

I recall here my setup: WinXP, python 2.4.2, wxPython 2.6.1.0, 
pythoncard 0.8.1

After some searching on the internet i found the following on 
http://www.wxwindows.org/prepare.htm
concerning preparing for wxWidgets 2:
"
Be aware that under Windows, *font sizes will change* to match standard 
Windows font sizes (for example, a 12-point font will appear bigger than 
before). Write your application to be flexible where fonts are 
concerned. Don't rely on fonts being similarly-sized across platforms, 
as they were (by chance) between Windows and X under wxWidgets 1.66. 
Yes, this is not easy... but I think it's better to conform to the 
standards of each platform, and currently the size difference makes it 
difficult to conform to Windows UI standards. You may eventually wish to 
build in a global 'fudge-factor' to compensate for size differences. The 
old font sizing will still be available via wx_setup.h, so do not panic...
"
Does that give any clue ?

Ronny

Alex Tweedly wrote:

> Ronny De Winter wrote:
>
>> Alex, you might be right that it is the default font. 
>
>
> Or I might not :-(
> I noticed that your euronext browser specifies the font size for the 
> multiColumnList.
>
>> I have similar problems with some of the PythonCard samples, ie. in 
>> the mp3player the buttons almost completely dissappear at the bottom 
>> of the window. Another example is minimalList which ads an horizontal 
>> scrollbar.
>>
>> Where are these default fonts set ?  Somewhere in wxPython or 
>> wxWindows ?
>>
> Probably in wxWidgets - but because at least one instance that causes 
> a problem has a font size specification, I'm not sure default fonts 
> are the answer. Sorry - not sure what it can be (and since it always 
> looks ok for me here, I'm not sure what to look at next).
>
> Some thoughts you could look at ...
> How does it look in the resorceEditor ?
> How do the wxDemo apps look (note you'll probably need to compare to 
> screenshots, because those apps that use sizers will probably 
> auto-adjust to look OK; only exception is where there is text/button 
> aligned with a fixed size graphic - like your "Update"button).
>
>

Re: [Pythoncard-users] Background events

[Brad A. <bra...@ma...>]

Don Taylor wrote:

>Is there a list somewhere of which events can be handled by the Background?
>Or, which code should I look at to fiigure this out?

Here is a list of some of the events that can be handled, but it's 
not complete.

http://pythoncard.sourceforge.net/framework/events_and_handlers.html

Re: [Pythoncard-users] layout and font problems

[Alex T. <al...@tw...>]

Ronny De Winter wrote:

> Alex, you might be right that it is the default font. 

Or I might not :-(
I noticed that your euronext browser specifies the font size for the 
multiColumnList.

> I have similar problems with some of the PythonCard samples, ie. in 
> the mp3player the buttons almost completely dissappear at the bottom 
> of the window. Another example is minimalList which ads an horizontal 
> scrollbar.
>
> Where are these default fonts set ?  Somewhere in wxPython or wxWindows ?
>
Probably in wxWidgets - but because at least one instance that causes a 
problem has a font size specification, I'm not sure default fonts are 
the answer. Sorry - not sure what it can be (and since it always looks 
ok for me here, I'm not sure what to look at next).

Some thoughts you could look at ...
How does it look in the resorceEditor ?
How do the wxDemo apps look (note you'll probably need to compare to 
screenshots, because those apps that use sizers will probably 
auto-adjust to look OK; only exception is where there is text/button 
aligned with a fixed size graphic - like your "Update"button).


-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] Background events

[Alex T. <al...@tw...>]

Don Taylor wrote:

> Is there a list somewhere of which events can be handled by the 
> Background?  Or, which code should I look at to fiigure this out?

I don't think there is, because it's an aspect of the control for which 
the event is initially generated, but which has no control-specific 
handler - not an aspect of the background.

Or to say it another way, the background should be able to handle any 
event which could have been handled by any control, simply by specifying 
the general handler (on_<event>) rather than the control-specific one 
(on_<control>_<event>), but the events will only occur relative to those 
controls which could have handled the event.

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] Re: Upgrade to wxPython 2.6.1

[Alex T. <al...@tw...>]

Don Taylor wrote:

> Alex Tweedly wrote:
>
>>
>> I upgraded last night from wxPython 2.5.3.1 to wxPython 2.6.1, and 
>> have found one problem.
>>
>> The advanced codeEditor (tools/oneEditor/tabcodeEditor.py) displays 
>> drop-downs for the list of components and (sometimes) for the 
>> handlers of that component - these are at the top of the window, 
>> above the tabbed notebook. Since the upgrade, the notebook covers the 
>> whole window area, and so these drop-downs are not visible or 
>> accessible.
>>
>
> I am running with wxPython 2.6.1 (on WinXP SP2 and Python 2.4) and I 
> do see the drop-downs in tabcodeEditor.

Thanks Don.
It appears that wxPython2.6.1 is *sometimes* more aggressive in 
calculating a min size for components than 2.5.x was, so much so that 
the Choice component is given "0" for height (and sometimes also a too 
small width).

I've added a spacer to the sizer set-up, as well as a min size in the 
resource file to my local copy, and that now works fine in every case 
I've found; if I see no problem after some more testing, I'll put that 
change into CVS.

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] layout and font problems

[Ronny De W. <ron...@gm...>]

Alex Tweedly wrote:

> Ronny De Winter wrote:
>
>> Alex Tweedly wrote:
>>
>>> Nice app!
>>> Looks fine to me here (WinXP home, PythonCard cvs latest, wxPython 
>>> 2.6.1, Python 2.3.4) - it matches the screenshot on SourceForge 
>>> (except for having the additional buttons).
>>>
>>> I'll try it with Python 2.4 this weekend if I can find a machine 
>>> with 2.4 on it already (don't want to up date my two main ones in 
>>> case of any problems).
>>>
> I was right to not want to risk the upgrade - I went ahead and did it, 
> and managed to break my WindIDE in the process :-(
>
>> You can find a Screencopy on 
>> http://www.5consulting.com/img/tmp/QuotesViewer-2005-12-17.jpg
>> Some differences:
>> - font of the table text is larger compared to buttons
>> - horizontal scrollbar because table width does not fit anymore
>> - watchlist buttons overlap with market selection
>> - "Market" string now in blue
>> - Update button falls out of the window
>>
>> Switching to Windows classic view gives similar problems.
>
>
> I upgraded to Python 2.4.1 and it still looks fine in both Win Classic 
> and WinXP themes (except for the "Market" string being blue).
>
> The screen shot looks just like something has made your default font 
> larger.
> How do the Pythoncard samples look ?  Do other PythonCard programs 
> have the same problem ?
>
> How about the wxPython demos ?  (though most of them use sizers, so 
> that may not tell us so much).
>
Alex, you might be right that it is the default font. I have similar 
problems with some of the PythonCard samples, ie. in the mp3player the 
buttons almost completely dissappear at the bottom of the window. 
Another example is minimalList which ads an horizontal scrollbar.

Where are these default fonts set ?  Somewhere in wxPython or wxWindows ?

Ronny

Re: [Pythoncard-users] Pythoncard in the Eclipse/Pydev debugger throws an exception on File->Exit

[Alex T. <al...@tw...>]

Don Taylor wrote:

> I don't know if this is a real bug, or an artifact of the running 
> Pythoncard apps under Eclipse/Pydev.  When, for example, Minimal is 
> run under the Pydev debugger it always throws the following exception 
> when File->Exit is selected.
>
> "Exception exceptions.TypeError: "'NoneType' object is not callable" 
> in <bound method Pen.__del__ of <wx._gdi.Pen; proxy of C++ wxPen 
> instance at _505f2602_p_wxPen>> ignored"
>
> When I run (rather than debug) Minimal under Pydev then I don't see 
> this exception being thrown.
>
> In general, I am able to set breakpoints and trace execution of 
> Pythoncard apps under Pydev.  This exception does not seem to cause 
> any harm as the app is about to die anyway.  I am curious as to 
> whether debugging under Pydev is generally going to work as I would 
> love to use Pythoncard running inside a rich OSS IDE like Eclipse (or 
> Netbeans).

I don't specifically know about Eclipse.

In WingIDE, there are some spurious exceptions reported; the WingIDE 
docs explain that they are sometimes unable to determine if an exception 
is being caught or not, and say that exceptions which are not reported 
when the app is run outside the debugger are likely to be instances of 
this problem - and the advised action is to mark them as "Ignore this 
exception" (or some similar thing). I've always done that and had no 
problems.

(Except that now I can't debug in WingIDE at all - but that's got to be 
just a side-effect of me messing around with versions of Python 
incorrectly. I hope.)

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] Re: How to report bugs?

[Alex T. <al...@tw...>]

Don Taylor wrote:

> I think that there is also a problem in this bit of code on the last 
> page of the "How to add a child window" walkthrough:
>
>      def doExit(self):
>         self.parent.components.field1.text = "99"
>
>     def on_close(self, event):
>         self.doExit()
>         self.visible = False
>
>     def on_menuFileExit_select(self, event):
>         self.close()
>
> The on_menuFileExit_select event does not seem to get fired anymore so 
> the code and the description need to be changed.
>
You're right, the doc should be changed (see below)

> Don.
>
> PS.  Is it simply not possible to intercept File->Exit events now, or 
> is there some other event that can be used instead?
>
It is possible to intercept File->Exit, just as before.

The reason it's not being fired in the child window walkthrough, is that 
the "Counter" example being used is derived from the Minimal sample - 
and "minimal" now uses a "command" for its menus. (In minimal.rsrc.py, 
you'll see

>
>     'menubar':
>     {
>         'type':'MenuBar',
>         'menus':
>         [
>             { 'type':'Menu',
>               'name':'menuFile',
>               'label':'&File',
>               'items': [
>                 { 'type':'MenuItem',
>                   'name':'menuFileExit',
>                   'label':'E&xit\tAlt+X',
>                   'command':'exit' } ] }
>         ]       
>     },

Because the File/Exit entry has a command defined, it triggers that 
instead of the menu select event.

So the code fragment should be changed from

>     def on_menuFileExit_select(self, event):
>         self.close()

to

>     def on_exit_command(self, event):
>         self.close()

(and enough explanatory text should be added to explain this ....)


-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[Alex T. <al...@tw...>]

Ronny De Winter wrote:

> Alex Tweedly wrote:
>
>> Nice app!
>> Looks fine to me here (WinXP home, PythonCard cvs latest, wxPython 
>> 2.6.1, Python 2.3.4) - it matches the screenshot on SourceForge 
>> (except for having the additional buttons).
>>
>> I'll try it with Python 2.4 this weekend if I can find a machine with 
>> 2.4 on it already (don't want to up date my two main ones in case of 
>> any problems).
>>
I was right to not want to risk the upgrade - I went ahead and did it, 
and managed to break my WindIDE in the process :-(

> You can find a Screencopy on 
> http://www.5consulting.com/img/tmp/QuotesViewer-2005-12-17.jpg
> Some differences:
> - font of the table text is larger compared to buttons
> - horizontal scrollbar because table width does not fit anymore
> - watchlist buttons overlap with market selection
> - "Market" string now in blue
> - Update button falls out of the window
>
> Switching to Windows classic view gives similar problems.

I upgraded to Python 2.4.1 and it still looks fine in both Win Classic 
and WinXP themes (except for the "Market" string being blue).

The screen shot looks just like something has made your default font 
larger.
How do the Pythoncard samples look ?  Do other PythonCard programs have 
the same problem ?

How about the wxPython demos ?  (though most of them use sizers, so that 
may not tell us so much).

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005

Re: [Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[Ronny De W. <ron...@gm...>]

Alex Tweedly wrote:

> Ronny De Winter wrote:
>
>> Alex Tweedly wrote:
>>
>>> ronny de winter wrote:
>>>
>>>> Also the layout does not fit (overlapping buttons, window too 
>>>> small, etc ...),
>>>> guess this is due to the new wxPython version, the application was 
>>>> originally build with
>>>> wxPython2.5.2
>>>>
>>>> Anybody experienced similar problems or have some tips ?
>>>
>>>
>>>
>>>
>>> Which layout does not fit ?
>>> Is it one of the tools (or samples) ? Or one of your own ?
>>> If it's your own - is it something you can send to let me look at 
>>> it; I've recently moved to wxPython 2.6.1 and I don't see any 
>>> problems with layouts changing.
>>>
>> It is my own application. You can download it at 
>> http://quotesviewer.sourceforge.net
>> Or might it be WinNT vs WinXP ?, allthough i seem to remember that it 
>> waas ok before on WinNT and WinXP.
>
>
> Nice app!
> Looks fine to me here (WinXP home, PythonCard cvs latest, wxPython 
> 2.6.1, Python 2.3.4) - it matches the screenshot on SourceForge 
> (except for having the additional buttons).
>
> I'll try it with Python 2.4 this weekend if I can find a machine with 
> 2.4 on it already (don't want to up date my two main ones in case of 
> any problems).
>
You can find a Screencopy on 
http://www.5consulting.com/img/tmp/QuotesViewer-2005-12-17.jpg
Some differences:
- font of the table text is larger compared to buttons
- horizontal scrollbar because table width does not fit anymore
- watchlist buttons overlap with market selection
- "Market" string now in blue
- Update button falls out of the window

Switching to Windows classic view gives similar problems.

Ronny De Winter
http://quotesviewer.sourceforge.net

[Pythoncard-users] Background events

[Don T. <nos...@gm...>]

Is there a list somewhere of which events can be handled by the 
Background?  Or, which code should I look at to fiigure this out?

Thanks,

Don.

[Pythoncard-users] Re: How to report bugs?

[Don T. <nos...@gm...>]

I think that there is also a problem in this bit of code on the last 
page of the "How to add a child window" walkthrough:

      def doExit(self):
         self.parent.components.field1.text = "99"

     def on_close(self, event):
         self.doExit()
         self.visible = False

     def on_menuFileExit_select(self, event):
         self.close()

The on_menuFileExit_select event does not seem to get fired anymore so 
the code and the description need to be changed.

Don.

PS.  Is it simply not possible to intercept File->Exit events now, or is 
there some other event that can be used instead?

[Pythoncard-users] Re: Upgrade to wxPython 2.6.1

[Don T. <nos...@gm...>]

Alex Tweedly wrote:
> 
> I upgraded last night from wxPython 2.5.3.1 to wxPython 2.6.1, and have 
> found one problem.
> 
> The advanced codeEditor (tools/oneEditor/tabcodeEditor.py) displays 
> drop-downs for the list of components and (sometimes) for the handlers 
> of that component - these are at the top of the window, above the tabbed 
> notebook. Since the upgrade, the notebook covers the whole window area, 
> and so these drop-downs are not visible or accessible.
> 
> I'll take a look at it this weekend, but if anyone already knows of 
> changes to sizer behaviour, or anything else, that might cause this 
> change, please let me know.
> 
Alex:

I am running with wxPython 2.6.1 (on WinXP SP2 and Python 2.4) and I do 
see the drop-downs in tabcodeEditor.

Don.

[Pythoncard-users] Pythoncard in the Eclipse/Pydev debugger throws an exception on File->Exit

[Don T. <nos...@gm...>]

I don't know if this is a real bug, or an artifact of the running 
Pythoncard apps under Eclipse/Pydev.  When, for example, Minimal is run 
under the Pydev debugger it always throws the following exception when 
File->Exit is selected.

"Exception exceptions.TypeError: "'NoneType' object is not callable" in 
<bound method Pen.__del__ of <wx._gdi.Pen; proxy of C++ wxPen instance 
at _505f2602_p_wxPen>> ignored"

When I run (rather than debug) Minimal under Pydev then I don't see this 
exception being thrown.

In general, I am able to set breakpoints and trace execution of 
Pythoncard apps under Pydev.  This exception does not seem to cause any 
harm as the app is about to die anyway.  I am curious as to whether 
debugging under Pydev is generally going to work as I would love to use 
Pythoncard running inside a rich OSS IDE like Eclipse (or Netbeans).

Don.

Re: [Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[Alex T. <al...@tw...>]

Ronny De Winter wrote:

> Alex Tweedly wrote:
>
>> ronny de winter wrote:
>>
>>> Also the layout does not fit (overlapping buttons, window too small, 
>>> etc ...),
>>> guess this is due to the new wxPython version, the application was 
>>> originally build with
>>> wxPython2.5.2
>>>
>>> Anybody experienced similar problems or have some tips ?
>>
>>
>>
>> Which layout does not fit ?
>> Is it one of the tools (or samples) ? Or one of your own ?
>> If it's your own - is it something you can send to let me look at it; 
>> I've recently moved to wxPython 2.6.1 and I don't see any problems 
>> with layouts changing.
>>
> It is my own application. You can download it at 
> http://quotesviewer.sourceforge.net
> Or might it be WinNT vs WinXP ?, allthough i seem to remember that it 
> waas ok before on WinNT and WinXP.

Nice app!
Looks fine to me here (WinXP home, PythonCard cvs latest, wxPython 
2.6.1, Python 2.3.4) - it matches the screenshot on SourceForge (except 
for having the additional buttons).

I'll try it with Python 2.4 this weekend if I can find a machine with 
2.4 on it already (don't want to up date my two main ones in case of any 
problems).

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005

Re: [Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[Ronny De W. <ron...@gm...>]

Alex Tweedly wrote:

> ronny de winter wrote:
>
>> Hi,
>>
>> I am on Windows XP home, installed python 2.4.2, wxPython 2.6.1.0 
>> <http://2.6.1.0>
>> Installation of pythoncard 0.8.1 fails very close near the end.
>> My pythoncard app works. But pythoncard is not added to the start 
>> program list.
>>
> Did you use
> PythonCard-0.8.1.win32.exe 
> <http://prdownloads.sourceforge.net/pythoncard/PythonCard-0.8.1.win32.exe?download>
> or
> PythonCard-0.8.1.FIXED.win32.exe 
> <http://prdownloads.sourceforge.net/pythoncard/PythonCard-0.8.1.FIXED.win32.exe?download>  
> ?
>
Ok thanks, that was the problem. PythonCard-0.8.1.FIXED.win32.exe works 
fine!

> ronny de winter wrote:
>
>> Also the layout does not fit (overlapping buttons, window too small, 
>> etc ...),
>> guess this is due to the new wxPython version, the application was 
>> originally build with
>> wxPython2.5.2
>>
>> Anybody experienced similar problems or have some tips ?
>
>
> Which layout does not fit ?
> Is it one of the tools (or samples) ? Or one of your own ?
> If it's your own - is it something you can send to let me look at it; 
> I've recently moved to wxPython 2.6.1 and I don't see any problems 
> with layouts changing.
>
It is my own application. You can download it at 
http://quotesviewer.sourceforge.net
Or might it be WinNT vs WinXP ?, allthough i seem to remember that it 
waas ok before on WinNT and WinXP.

>-- 
>Alex Tweedly       http://www.tweedly.net
>  
>
>------------------------------------------------------------------------
>
>No virus found in this outgoing message.
>Checked by AVG Free Edition.
>Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005
>  
>

Re: [Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[Alex T. <al...@tw...>]

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005

[Pythoncard-users] pythoncard 0.8.1 Windows installer failure

[ronny de w. <ron...@gm...>]

Hi,

I am on Windows XP home, installed python 2.4.2, wxPython 2.6.1.0
Installation of pythoncard 0.8.1 fails very close near the end.
My pythoncard app works. But pythoncard is not added to the start program
list.

Also the layout does not fit (overlapping buttons, window too small, etc
...),
guess this is due to the new wxPython version, the application was
originally build with
wxPython2.5.2

Anybody experienced similar problems or have some tips ?

Best regards,
Ronny De Winter
http://quotesviewer.sourceforge.net

Re: [Pythoncard-users] Minimizing an application?

[Alex T. <al...@tw...>]

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005

[Pythoncard-users] Upgrade to wxPython 2.6.1

[Alex T. <al...@tw...>]

I upgraded last night from wxPython 2.5.3.1 to wxPython 2.6.1, and have 
found one problem.

The advanced codeEditor (tools/oneEditor/tabcodeEditor.py) displays 
drop-downs for the list of components and (sometimes) for the handlers 
of that component - these are at the top of the window, above the tabbed 
notebook. Since the upgrade, the notebook covers the whole window area, 
and so these drop-downs are not visible or accessible.

I'll take a look at it this weekend, but if anyone already knows of 
changes to sizer behaviour, or anything else, that might cause this 
change, please let me know.

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005

Re: [Pythoncard-users] Re: PythonCard, Eclipse and Pydev

[Alex T. <al...@tw...>]

Don Taylor wrote:

> Alex Tweedly wrote:
>
>> - has a drop-down for all controls in the current file
>>       Selecting one of them makes another drop-down appear.
>>       This shows all events for that control type, with a "+" marking 
>> those for which a handler exists.
>> <etc.>
>
>
> Oh, this looks very handy indeed.  Thanks.
>
> What about a facility for adding background event handlers too?  I 
> initialize mentioned in a tutorial, but I can't find a refernce to any 
> others.
>
They aren't used all that often (or at least, I don't use them that often).

They aren't true "background" handlers in the Hypercard sense, so you 
need to be careful (though given that I've never used Hypercard, my 
interpretation may be slightly off ....)

You can create a handler, say on_mouseMove. If there is a component 
which could have had a mouseMove handler, but doesn't, then those events 
go to the "background" handler instead. But there is no mouseMove event 
generated when the mouse is moved while not over any component, nor 
while over a component that doesn't support mouseMove.

Since the code inserted is so minimal, I'm not sure it's worth adding a 
method to insert background handlers - easy enough to do manually, or to 
add a handler to a component and remove the component name (i.e. edit 
"on_someComponent_event" to be just "on_event")

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/204 - Release Date: 15/12/2005

Re: [Pythoncard-users] How to report bugs?

[Alex T. <al...@tw...>]

[re-ordered for simplicity in getting my replies in the right order ....]

Andrew Todd wrote:

>
> I must admit to not checking the SourceForge issues as often as I 
> should , but please do use it to report bugs. It never harms to 
> mention them on this mailing list as well though.
>
> The advantage to using the SourceForge bug trackers are that issues 
> never get lost, unlike on a mailing list where it's very difficult to 
> keep a coherent view of the outstanding work.

I confess I had never looked at the Bugs listed on SourceForge - I was 
just totally unaware of it as a place to either report bugs or check for 
them. I'll try to look regularly from now on. But as Andy says, 
definitely report bugs in SourceForge, and can't hurt to mention them on 
the mailing list as well.

> Don Taylor wrote:
>
>> I was going to report the following as a documentation bug against 
>> the PythonCard project on SourceSafe but it does not look as if the 
>> bugs already reported there are being handled.
>>
Note that for documentation bugs it can be confusing whether you are 
looking at the docs as supplied by your version of PythonCard or on the 
web site. I did a number of updates to the docs (particularly the 
walkthroughs) a while ago - so they are in CVS but not yet reflected by 
what you see on the web site; your local, latest copy is in 
PythonCard/docs/html

I guess the web site can't be updated until there is a new release, in 
case the docs get ahead of the released code.

>> Errors and inconsistencies in the "Getting Started in PythonCard" 
>> walkthroughs
>>
>> 1) The only piece of code in the first walkthrough that it asks you 
>> to look at and change in the 'Minimal' application is no longer there 
>> because menuFileExit handling is now done automatically.
>>
Already fixed in CVS.

>> 2) The second walkthrough refers to an "Add Button" item in the 
>> Components menu of the resourceEditor.  This is now replaced with a 
>> "Button" item together with a dialog box that is not described in the 
>> walkthrough.
>>
Oops - missed that one. I'll probably leave it for the moment too - I 
have a long-term scheme to replace the "basic" resourceEditor with the 
new multi-component capable resourceEditor (in 
tools/resourceEditor/multiresourceEditor.py) which has a different set 
of dialogs, and will require a further significant upgrade of the docs.

>> 3) The Python indentation in the first code sample screenshot is 
>> incorrect.  The code as shown does not work.
>>
Already fixed in CVS.

Thanks
-- Alex

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.13.13/200 - Release Date: 14/12/2005

Re: [Pythoncard-users] How to report bugs?

[Andrew T. <an...@ha...>]

Don Taylor wrote:
> I was going to report the following as a documentation bug against the 
> PythonCard project on SourceSafe but it does not look as if the bugs 
> already reported there are being handled.
> 
> Is this so?  Or maybe there is some other way to report bugs?
> 
> Don.
> 
> 
> Errors and inconsistencies in the "Getting Started in PythonCard" 
> walkthroughs
> 
> 1) The only piece of code in the first walkthrough that it asks you to 
> look at and change in the 'Minimal' application is no longer there 
> because menuFileExit handling is now done automatically.
> 
> 2) The second walkthrough refers to an "Add Button" item in the 
> Components menu of the resourceEditor.  This is now replaced with a 
> "Button" item together with a dialog box that is not described in the 
> walkthrough.
> 
> 3) The Python indentation in the first code sample screenshot is 
> incorrect.  The code as shown does not work.
> 

I must admit to not checking the SourceForge issues as often as I should 
, but please do use it to report bugs. It never harms to mention them on 
this mailing list as well though.

The advantage to using the SourceForge bug trackers are that issues 
never get lost, unlike on a mailing list where it's very difficult to 
keep a coherent view of the outstanding work.

Regards,
Andy
-- 
--------------------------------------------------------------------------------
 From the desk of Andrew J Todd esq - http://www.halfcooked.com/

[Pythoncard-users] Re: PythonCard, Eclipse and Pydev

[Don T. <nos...@gm...>]

Alex Tweedly wrote:

> It's not in the "normal" codeEditor, it's in the "advanced" version, 
> which can be found, rather confusingly, in
>  PythonCard/tools/oneEditor/tabcodeEditor.py
> 
> Has two features not in the basic editor
> - uses tabbed notebook to allow multiple files to be edited
> - has a drop-down for all controls in the current file
>       Selecting one of them makes another drop-down appear.
>       This shows all events for that control type, with a "+" marking 
> those for which a handler exists.
> 
> Selecting one of those will position the cursor on the first line of the 
> handler.
> Selecting one for which no handler exists yet will insert a "blank" handler
>               (without ensuring your on a blank line - use with care :-)
> 
> This "advanced" editor is "experimental" - hasn't been as widely used or 
> tested as the basic one, so use with care. Having said that, I've used 
> it almost exclusively for many months and had only one (repeated) glitch 
> (something to do with opening new windows while the shell window is open 
> - but couldn't reproduce it).
> 

Oh, this looks very handy indeed.  Thanks.

What about a facility for adding background event handlers too?  I 
initialize mentioned in a tutorial, but I can't find a refernce to any 
others.

Don.

[Pythoncard-users] How to report bugs?

[Don T. <nos...@gm...>]

I was going to report the following as a documentation bug against the 
PythonCard project on SourceSafe but it does not look as if the bugs 
already reported there are being handled.

Is this so?  Or maybe there is some other way to report bugs?

Don.


Errors and inconsistencies in the "Getting Started in PythonCard" 
walkthroughs

1) The only piece of code in the first walkthrough that it asks you to 
look at and change in the 'Minimal' application is no longer there 
because menuFileExit handling is now done automatically.

2) The second walkthrough refers to an "Add Button" item in the 
Components menu of the resourceEditor.  This is now replaced with a 
"Button" item together with a dialog box that is not described in the 
walkthrough.

3) The Python indentation in the first code sample screenshot is 
incorrect.  The code as shown does not work.