Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #3542 > unrolled thread

Want to save recoding

Started byMartin <spam@spam.spam>
First post2012-05-31 15:16 +0100
Last post2012-05-31 16:45 +0100
Articles 4 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Want to save recoding Martin <spam@spam.spam> - 2012-05-31 15:16 +0100
    Re: Want to save recoding "Willie Moore" <williem@wmconsulting.com> - 2012-05-31 10:26 -0500
      Re: Want to save recoding Martin <spam@spam.spam> - 2012-05-31 16:35 +0100
      Re: Want to save recoding Martin <spam@spam.spam> - 2012-05-31 16:45 +0100

#3542 — Want to save recoding

FromMartin <spam@spam.spam>
Date2012-05-31 15:16 +0100
SubjectWant to save recoding
Message-ID<m3Lxr.861991$m91.824338@fx24.am4>
I will have about 20 screens all with the same code, but with 3 or 4 
different layouts.

I could use one class for this and move fields around in postinits, but 
is there any way to refer to a browser object from the base class into 
the screens class.

I KNOW I can do it but break editabilty by having the inits and stuff in 
their own classes. But this would be painfull.

Thanks

Martin

[toc] | [next] | [standalone]


#3543

From"Willie Moore" <williem@wmconsulting.com>
Date2012-05-31 10:26 -0500
Message-ID<jq82ip$1va$1@speranza.aioe.org>
In reply to#3542
Martin,

How I have done this in the past is to create a base class with the business 
logic for how the browser is supposed to be set up. then on each screen I 
add a browser (each screen uses the same name) and in my postinit I call my 
base class setup to make sure that each is handled the same way. All of the 
callback methods are in the base class.

In the dotNet world, I would create a base class with associated form. You 
can then use that form as the basis for another form. Dieter did a really 
good article on visual inheritance with Vulcan.net.

Regards,
Willie
Vulcan VIP

"Martin"  wrote in message news:m3Lxr.861991$m91.824338@fx24.am4...

I will have about 20 screens all with the same code, but with 3 or 4
different layouts.

I could use one class for this and move fields around in postinits, but
is there any way to refer to a browser object from the base class into
the screens class.

I KNOW I can do it but break editabilty by having the inits and stuff in
their own classes. But this would be painfull.

Thanks

Martin 

[toc] | [prev] | [next] | [standalone]


#3544

FromMartin <spam@spam.spam>
Date2012-05-31 16:35 +0100
Message-ID<6dMxr.816606$8q1.422723@fx29.am4>
In reply to#3543
Thanks

My trial with resizing failed - the base screen did not change size

On 31/05/2012 16:26, Willie Moore wrote:
> Martin,
>
> How I have done this in the past is to create a base class with the
> business logic for how the browser is supposed to be set up. then on
> each screen I add a browser (each screen uses the same name) and in my
> postinit I call my base class setup to make sure that each is handled
> the same way. All of the callback methods are in the base class.
>
> In the dotNet world, I would create a base class with associated form.
> You can then use that form as the basis for another form. Dieter did a
> really good article on visual inheritance with Vulcan.net.
>
> Regards,
> Willie
> Vulcan VIP
>
> "Martin" wrote in message news:m3Lxr.861991$m91.824338@fx24.am4...
>
> I will have about 20 screens all with the same code, but with 3 or 4
> different layouts.
>
> I could use one class for this and move fields around in postinits, but
> is there any way to refer to a browser object from the base class into
> the screens class.
>
> I KNOW I can do it but break editabilty by having the inits and stuff in
> their own classes. But this would be painfull.
>
> Thanks
>
> Martin

[toc] | [prev] | [next] | [standalone]


#3545

FromMartin <spam@spam.spam>
Date2012-05-31 16:45 +0100
Message-ID<LmMxr.649188$Yw1.237155@fx12.am4>
In reply to#3543
Put Self:Dimension := whatever on the postinit - has no effect on a 
tabbed dialogue!!!!

On 31/05/2012 16:26, Willie Moore wrote:
> Martin,
>
> How I have done this in the past is to create a base class with the
> business logic for how the browser is supposed to be set up. then on
> each screen I add a browser (each screen uses the same name) and in my
> postinit I call my base class setup to make sure that each is handled
> the same way. All of the callback methods are in the base class.
>
> In the dotNet world, I would create a base class with associated form.
> You can then use that form as the basis for another form. Dieter did a
> really good article on visual inheritance with Vulcan.net.
>
> Regards,
> Willie
> Vulcan VIP
>
> "Martin" wrote in message news:m3Lxr.861991$m91.824338@fx24.am4...
>
> I will have about 20 screens all with the same code, but with 3 or 4
> different layouts.
>
> I could use one class for this and move fields around in postinits, but
> is there any way to refer to a browser object from the base class into
> the screens class.
>
> I KNOW I can do it but break editabilty by having the inits and stuff in
> their own classes. But this would be painfull.
>
> Thanks
>
> Martin

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web