On 01/01/2015 05:59 PM, Tobias Boege wrote:
> On Thu, 01 Jan 2015, Stephen wrote:
>> The only way that I can see out of my conundrum is to create a
>> property in in each form to which updated information is to be pushed.
>> The property write will process the received data and put it where i
this is the good POO way !
2015-01-01 23:39 GMT+01:00 Stephen :
> When, at the project level, all controls on all forms are set to be
> public, the 'Public' property for each control on each form continues to
> indicate that it is NOT Public. This is misleading.
>
>The 'Public' property of
On Thu, 01 Jan 2015, Stephen wrote:
>The only way that I can see out of my conundrum is to create a
> property in in each form to which updated information is to be pushed.
> The property write will process the received data and put it where it
> needs to go.
>
Sounds suspiciously like you
When, at the project level, all controls on all forms are set to be
public, the 'Public' property for each control on each form continues to
indicate that it is NOT Public. This is misleading.
The 'Public' property of all controls should reflect the reality,
that it is publicly visible,
Am Donnerstag, den 01.01.2015, 21:57 +0100 schrieb Tobias Boege:
> On Thu, 01 Jan 2015, Stephen wrote:
> > I just extracted the archive from the email, loaded it and of course it
> > works perfectly.
> >
> > I had this;
> >
> > mhform1.textbox2.text = value
> >
> > and
> >
> > mgform2.textbox2
On Thu, 01 Jan 2015, Stephen wrote:
> I just extracted the archive from the email, loaded it and of course it
> works perfectly.
>
> I had this;
>
> mhform1.textbox2.text = value
>
> and
>
> mgform2.textbox2.text = value
>
> in my original code but I kept getting "null object" every time it t
I just extracted the archive from the email, loaded it and of course it
works perfectly.
I had this;
mhform1.textbox2.text = value
and
mgform2.textbox2.text = value
in my original code but I kept getting "null object" every time it tried
execute the line.
Thanks for putting up with my stupi
On Tue, 30 Dec 2014, Charlie Reinl wrote:
> Am Dienstag, den 30.12.2014, 16:45 +0100 schrieb Tobias Boege:
> > On Tue, 30 Dec 2014, Charlie Reinl wrote:
> > > Am Dienstag, den 30.12.2014, 07:27 -0500 schrieb Stephen:
> > > > Attached is a test harness that tries to implement the following.
> > > >
Am Dienstag, den 30.12.2014, 16:45 +0100 schrieb Tobias Boege:
> On Tue, 30 Dec 2014, Charlie Reinl wrote:
> > Am Dienstag, den 30.12.2014, 07:27 -0500 schrieb Stephen:
> > > Attached is a test harness that tries to implement the following.
> > >
> > >FormMain hosts two other forms (Form1 and
On Tue, 30 Dec 2014, Charlie Reinl wrote:
> Am Dienstag, den 30.12.2014, 07:27 -0500 schrieb Stephen:
> > Attached is a test harness that tries to implement the following.
> >
> >FormMain hosts two other forms (Form1 and Form2) within two frames
> > (Frame1 and Frame2). On each of these hoste
Am Dienstag, den 30.12.2014, 07:27 -0500 schrieb Stephen:
> Attached is a test harness that tries to implement the following.
>
>FormMain hosts two other forms (Form1 and Form2) within two frames
> (Frame1 and Frame2). On each of these hosted forms there are two text
> boxes and a button. Pr
Attached is a test harness that tries to implement the following.
FormMain hosts two other forms (Form1 and Form2) within two frames
(Frame1 and Frame2). On each of these hosted forms there are two text
boxes and a button. Pressing the button on either of the hosted forms
raises an event t
12 matches
Mail list logo
