Eric Bennett wrote:
He probably means being able to open multiple instances of a
window or being able to subclass window or control behavior.
I'm afraid I still don't get the exact point (I'm tired, sorry :-).
i dont know what i meant either (i was tired too).
Right now the only
Eric Bennett wrote:
This would be very helpful. The feature which would make this
complete for me is if each control had a tag value which could
hold a scalar reference.
a scalar reference to what?
Then it would be simple to segue into an OO approach:
sub CommonButtonName_Clicked {
Dave Moore wrote:
hey.
do event handler routines (ie. sub Button1_Click) have to be in
the main namespace or in the namespace in which they were created?
no, they can be anywhere: just add the namespace to your control's
name and the event will be searched in that namespace.
example:
On Fri, 2 Mar 2001, Aldo Calpini wrote:
it seems to me that this module wasnt really meant to be used in
an OO application? can anyone out there tell me otherwise?
I maybe be ignorant, but what the heck do you mean by 'an OO
application'? :-)
He probably means being able to open multiple
Eric Bennett wrote:
He probably means being able to open multiple instances of a
window or being able to subclass window or control behavior.
I'm afraid I still don't get the exact point (I'm tired, sorry :-).
Right now the only connection a control has to the rest of the
program is through
On Fri, 2 Mar 2001, Aldo Calpini wrote:
this is more clear. the New Event Model I'm trying to build will
pass a reference to the object that fired the event as its first
parameter, so this issue will be solved.
This would be very helpful. The feature which would make this complete
for me is
6 matches
Mail list logo
