Thanks to all those who ***isted me with my last question re: What is the
best way to produce WYSIWYG pages for viewing and printing.

I think that I have mastered the form with scrolling picture box method, it
looks fine but still lacks that windows application feel.

I was advised not to go the MDI form root at the time but no reason was
given. Could someone explain why not MDI form for the same purpose, I
understand that most MS applications use this approach?


Regards

Martin

On Mon, 16 Aug 2004 08:05:22 +0000 (UTC), "Martin"
<EMAIL REMOVED> wrote:

>Thanks to all those who ***isted me with my last question re: What is the
>best way to produce WYSIWYG pages for viewing and printing.
>
>I think that I have mastered the form with scrolling picture box method, it
>looks fine but still lacks that windows application feel.
>
>I was advised not to go the MDI form root at the time but no reason was
>given. Could someone explain why not MDI form for the same purpose, I
>understand that most MS applications use this approach?

Personally I reckon that the best bet is to export data to a
pseudo-text file and use another App to view/print the stuff

The time delay is negligable, it forces a data interchange format, and
it vastly simplifies the code of the 'real' Application

I'm not sure what you mean about the 'windows application feel'

However, if you just have one generic viewer to work on, the chances
are that you'll get it to look Ok

> Thanks to all those who ***isted me with my last question re: What is
the
> best way to produce WYSIWYG pages for viewing and printing.
>
> I think that I have mastered the form with scrolling picture box
method, it
> looks fine but still lacks that windows application feel.
>
> I was advised not to go the MDI form root at the time but no reason
was
> given. Could someone explain why not MDI form for the same purpose, I
> understand that most MS applications use this approach?

I'm not sure what control you are using for your WYSIWYG display, but if
it is a RichTextBox, then this link might be useful to you...

HOWTO: Set Up the RichTextBox Control for WYSIWYG Printing
http://support.microsoft.com/default...b;en-us;146022

Rick - MVP

--
Regards
I'm not actually using a RichTextBox.

My Controls are:- PictureBoxes, Labels and single line TextBoxes. These
controls are used on Data Input Forms and Result Forms.

As I say I have, I think, cracked the solutions for :-

1) Using a Form + Scrollbars with a full size Picture Box of the same size
as a printed A4 page. This solution gives me WYSIWYG, for screen/printer for
Data & Results Pages.

2) The second method that also appears to work satisfactorily is A MDIform
with Child Forms (instead of picture boxes) to represent the A4 Data Input
and Results Forms.

Functionally both methods are very similar except that I can have all the
form controls Minimise/Maximise/Close etc plus the ScrollBars all working
automatically (without programming). On the conventional Form +Scrolls +
PictureBox I would need to provide a good deal of programming to get the
equivalent Windows Feel.

As most of my programs can be of a similar style I have created Templates
for both methods, but would obviously like to continue with just one.

My first question to the group was "What is the best way?" and I was warned
away from the MDI approach.
My second question is obviously "Why not MDI?" when it seems to be giving me
more of an industry standard and requires less programming.

Regards
Martin

PS I have solved the earlier problem of restricted form length, the form can
be any length at design time and run time if in the correct mode.

Email: EMAIL REMOVED
Web Site: http://home.btconnect.com/cadoss

"Rick Rothstein" <EMAIL REMOVED> wrote in message
news:1_adncDOC-I3N73cRVn-EMAIL REMOVED...
> > Thanks to all those who ***isted me with my last question re: What is
> the
> > best way to produce WYSIWYG pages for viewing and printing.
> >
> > I think that I have mastered the form with scrolling picture box
> method, it
> > looks fine but still lacks that windows application feel.
> >
> > I was advised not to go the MDI form root at the time but no reason
> was
> > given. Could someone explain why not MDI form for the same purpose, I
> > understand that most MS applications use this approach?
>
> I'm not sure what control you are using for your WYSIWYG display, but if
> it is a RichTextBox, then this link might be useful to you...
>
> HOWTO: Set Up the RichTextBox Control for WYSIWYG Printing
> http://support.microsoft.com/default...b;en-us;146022
>
> Rick - MVP
>