Re: [Pythoncard-users] State of PythonCard

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

kc1...@ya... wrote:

> To Alex:
>
> The "layout editor" (I errornously referred to it as one of the =20
> resource editor) is not very stable for me.  When I use it, I get =20
> lots of failures and that's what I meant when I say "I have to click =20
> back and forth between the command window and the GUI window for it =20
> to be usable).  Towards the bottom of this email, I listed some of =20
> the messages I get (from just moving couple of the controls around) =20
> - it appears most problems are resize related.
>
Ah - OK. I have never seen these errors - can you please send version =20
info (i.e. which platform, os version, python,  wx, wxpython versions =20
and PythonCard version) and I'll see if I can reproduce them (or =20
failing that, if I can figure what the problem is without reproducing =20
them).

And a reminder to everyone - I (we) can't fix errors we don't know =20
about. And if John has previously reprted them, then I'm very sorry =20
for missing the report :-)

> And at one time it kept asking me not to double click...drives me =20
> nuts...but it doesn't seem to do that now
>
Yeah - that one was very irritating - I was on the point of simply =20
removing that error message, which was really only in there to let me =20
know that some "impossible" circumstance had happened and was being =20
ignored.

>
> Regarding the question of code generator, you said that the =20
> codeEditor does that?  How so?
When you're
  - in the code editor (the recent one - in oneEditor/codeEditor)
  - and  you use the drop-down list to select a component
the second drop-down now shows a list of events (with a "+" sign next =20
to those which have handlers defined).

If you seelct one of those so marked, then the editor moves you to the =20
first line of that handler.
If you select a new one (i.e. not marked with a "+"), the editor =20
inserts a blank handler for that event (beware - it does this at the =20
current cursor position - so you should position yourself at the start =20
of a blank line between handlers before doing this).

> Even if it does, it would be the wrong place to do that.  I think =20
> it's very counter-intuitive.   Within the resource editor, you see a =20
> control, and naturally you would say "I want this control to do ... =20
> when the user click, select, ... "
>
Currently the resource editor provides you no way to see or edit the =20
source code, so making changes to the source while in the =20
resourceEditor would be (IMHO) quite unnatural, even dangerous. When =20
we (some day) have a single integrated editor, then it would make =20
sense. But today, while in the resource editor it shouldn't (again, =20
just IMHO) be able to touch the source code. Apart from anything else, =20
I often (usually) have both resource and code editors open at the same =20
time, so any source code changes would be either ignored or (perhaps) =20
lost due to subsequent writing out the source code frm the codeEditor.


Thanks again for the tracebacks - I'll take a look at them (but the =20
version info would also help).

--=20
Alex Tweedly    al...@tw...   http://www.tweedly.net