🚀 go-pugleaf

It deals with it poorly. If you can code a public static method, then it can
call it, but otherwise the designer cant deal with other methods in the
source because it does not have an instance of the 'this' to call them with.
(It is instantiating the superclass and then instantiating the memeber
variables and applying applying the method calls it finds in jbInit to them.
So another possibility would be to put theses methods in the superclass, so
that if you design a file that extends the one that you are having problems
with, more of the method calls will work ).  Hopefully in the next release
the designer will be able to look into other methods that are referenced in
jbInit for additional property settings, but that probably wont help with
what you are expecting it to do.

Luc <luc.speleman@pdconsult.no> wrote in message news:38fc2866@dnews...
> I understand that all the graphics need to be in a jbInit method, but how
do
> you deal with
> other methods that also should be included in this jbInit method.
> For example : When I need to create a lot off text fields, I create a
method
> which receive the
> necessary parameters to create a textfield. This doesn't sound unusual I
> guess but the designer
> gives error that he doesn't find the makeField() method.
> How do you deal with that ?
>
> Luc
>
>