Re: [Pythoncard-users] PythonCard 0.8 issues (was Re: #pythoncard irc channel on freenode)

[Kevin A. <al...@se...>]

On Aug 23, 2004, at 3:32 PM, XXXXXXXXXXX wrote:

> On Mon, 23 Aug 2004 22:07:08 +0100, Alex Tweedly wrote:
>
>>
>> I'd suggest posting them to this list. IRC can be a good place to 
>> discuss
>> them if needed, but it's worth having them described on the mailing 
>> list so
>> that everyone can see them even if they don't happen to be on irc at 
>> the
>> right time.
>>
>
> OK, here are a few minor things I've discovered running 0.8 following 
> my
> upgrade to the latest versions of everything on Friday. Let's see if
> anybody else can replicate these or agree/disagree. I think I've 
> checked
> all the to-do and known bug lists, but if not please don't shout - I'm 
> a
> newbie!
>
> Unless I say otherwise, assume this applies to the OS X and Win32 
> versions...
>
> 1) Documentation - the on-line stuff is duplicated in the PythonCard/
> docs/html directory, but if I try to click on a link to any of the
> component descriptions they're not there. The components directory is
> missing. Not a huge problem when I have ADSL, but the one time I was
> network-less I tried using the docs and discovered this.

Tis true, but it is because you can generate those files yourself. This 
has been covered a few times before on the list, but it definitely 
needs to be highlighted better. Anyway, open up the widgets sample and 
select Create Component Docs... under the File menu, choose the 
PythonCard/docs/html/framework directory. Then you'll see that some 
idiot left the old 2.5.1.5 Blit API call in the code and so it throws 
an exception. Doh! So, then you get to "patch" your copy of widgets.py 
by changing line 374 from:

                 memdc.Blit((0, 0), w.size, dc, (0, 0))

to:

                 memdc.BlitPointSize((0, 0), w.size, dc, (0, 0))

Now try Create Component Docs... again and you should have your own 
copy, complete with widgets based on whatever platform you're running.

> 2) Typo - in the resource editor when you duplicate a component the
> offset widgets are spelt wrong - "Offest Horizontally", etc. :-)

I point the finger at the guy in the other country ;-)

> 3) Image path - this follows on from an observation I made recently. 
> When
> you select an image in the background dialog you can use the file 
> browser
> to track it down, but in the resource file the path is never stored and
> therefore the image fails to load unless it's in the same directory as
> the resource file.
>
> Now why you'd want to locate the image somewhere other than the current
> directory I couldn't say...

Yep, I should probably change the code to save a relative path so you 
could select a file and then have it be something like 
images/testo.jpg. I'll ponder that for the various places Image is 
used. I'm pretty sure relative paths already work, but there is  no 
attempt to break apart the path and then rejoin it so slashes are 
converted to backslashes, etc.

> 4) Colour...oops...Color picker - could this open with the property's
> current value? At the moment it always starts with black. Just makes it
> easier to make a minor color shift and makes the OS X color picker look
> better when it opens.

Yes it could. I just need to change a few lines so that the current 
color is passed in as the name arg to the colorDialog. Good one! I'll 
look at this along with the image path issue above tomorrow.

> Nothing earth-shattering, I admit, but a start.
>
> Neil

Hey, it is comments like these that keep the project moving forward!

ka