pythoncard-users

[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.

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/

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

[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?

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