On Thu, 27 Nov 2014, T Lee Davidson wrote:
> Wow. That is a very good explanation. Thank you, Tobi!
>
> I did understand that "a form is by default its own event observer". But
> I guess I did not fully understand exactly what that meant.
>
> (And, yes, I have seen code like, "Public Sub Form_Op
On 11/27/2014 02:36 PM, T Lee Davidson wrote:
> Wow. That is a very good explanation. Thank you, Tobi!
>
> I did understand that "a form is by default its own event observer". But
> I guess I did not fully understand exactly what that meant.
>
> (And, yes, I have seen code like, "Public Sub Form_Op
Wow. That is a very good explanation. Thank you, Tobi!
I did understand that "a form is by default its own event observer". But
I guess I did not fully understand exactly what that meant.
(And, yes, I have seen code like, "Public Sub Form_Open()", and always
wondered why it did not say "Form1_O
On Thu, 27 Nov 2014, Tobias Boege wrote:
> OK, "As name" comes as a bundle. It makes your newly created object raise
> events under the given name and makes the current class its event observer.
Read: ... current *object* its event observer.
--
"There's an old saying: Don't change anything... ev
On Thu, 27 Nov 2014, T Lee Davidson wrote:
> On 11/27/2014 12:55 PM, Tobias Boege wrote:
> > On Thu, 27 Nov 2014, T Lee Davidson wrote:
> >> On 11/27/2014 08:39 AM, Beno?t Minisini wrote:
> >>> Le 27/11/2014 14:29, Stephen a ?crit :
> I'm not consciously overriding the event observer so I'm no
On 11/27/2014 12:55 PM, Tobias Boege wrote:
> On Thu, 27 Nov 2014, T Lee Davidson wrote:
>> On 11/27/2014 08:39 AM, Beno?t Minisini wrote:
>>> Le 27/11/2014 14:29, Stephen a ?crit :
I'm not consciously overriding the event observer so I'm not clear how
to not do it.
Obviously I still
On Thu, 27 Nov 2014, T Lee Davidson wrote:
> On 11/27/2014 08:39 AM, Beno?t Minisini wrote:
> > Le 27/11/2014 14:29, Stephen a ?crit :
> >> I'm not consciously overriding the event observer so I'm not clear how
> >> to not do it.
> >> Obviously I still have much to learn.
> >>
> >
> > mhForm1 = New
On 11/27/2014 08:39 AM, Benoît Minisini wrote:
> Le 27/11/2014 14:29, Stephen a écrit :
>> I'm not consciously overriding the event observer so I'm not clear how
>> to not do it.
>> Obviously I still have much to learn.
>>
>
> mhForm1 = New Form1(TabStrip1) As "Form1"
>
On 11/27/2014 08:39 AM, Benoît Minisini wrote:
> Le 27/11/2014 14:29, Stephen a écrit :
>> I'm not consciously overriding the event observer so I'm not clear how
>> to not do it.
>> Obviously I still have much to learn.
>>
> mhForm1 = New Form1(TabStrip1) As "Form1"
>
Le 27/11/2014 14:29, Stephen a écrit :
> I'm not consciously overriding the event observer so I'm not clear how
> to not do it.
> Obviously I still have much to learn.
>
mhForm1 = New Form1(TabStrip1) As "Form1"
\/
.
I'm not consciously overriding the event observer so I'm not clear how
to not do it.
Obviously I still have much to learn.
On 11/27/2014 08:20 AM, Benoît Minisini wrote:
> Le 27/11/2014 14:08, Stephen a écrit :
>> GAMBAS: 3.5.4
>> Fedora 20 in a VM under 64 bit CentOS 6.5
>> MATE Desk
Le 27/11/2014 14:08, Stephen a écrit :
>GAMBAS: 3.5.4
>Fedora 20 in a VM under 64 bit CentOS 6.5
>MATE Desktop
>
>I'm a bit confused (some would say it's my normal state:) as to why,
> when a form is dynamically instantiated within a tabstrip (or other
> container) the Open and Show
GAMBAS: 3.5.4
Fedora 20 in a VM under 64 bit CentOS 6.5
MATE Desktop
I'm a bit confused (some would say it's my normal state:) as to why,
when a form is dynamically instantiated within a tabstrip (or other
container) the Open and Show events for the instantiated form don't
fire. This c
13 matches
Mail list logo
