Xojo Developer Conference
25/27th April 2018 in Denver.
MBS Xojo Conference
6/7th September 2018 in Munich, Germany.

Reasons for differences in printing on Mac and PC in 5.5? (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: Windows IDE installer locks up
Next thread: StyledText: Gaps?


Module Property Bug?   -   Richard Rhyan
  Reasons for differences in printing on Mac and PC in 5.5?   -   Brian Gaines
    Re: Reasons for differences in printing on Mac and PC in 5.5?   -   Joe Huber

Reasons for differences in printing on Mac and PC in 5.5?
Date: 28.02.04 19:14 (Sat, 28 Feb 2004 10:14:09 -0800)
From: Brian Gaines
I noticed that my app's printing was cut-off at the left and top
under Win32, and found a note in the release notes saying that there
was a "Fix" for Win" where the printed area was no longer offset by
the width and height of the non-printable area.

It is easy enough to reinstate the correct behavior by putting this
offset in oneself wherever printing occurs but, because the "Fix" was
only put in for Win32, one has to put in conditional compilation in
all printing situations. This seems a pity since one remarkable
feature of REALbasic is that the same project compiles for both Win32
and Mac with very little conditional compilation (and what is needed
generally reflects the differences in the underlying OS
functionalities, e.g. the need to put in one's own screen buffering
under Win32).

The "Fix" just makes the printer graphics object's origin the top
left of the actual page rather than that of the printable area, and
seems logical enough, but why was it done only for Win32? If the
cross-platform anomaly is deliberate then the Language Reference
needs to warn of the difference, but it does not.

Any insights?, b.

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: Reasons for differences in printing on Mac and PC in 5.5?
Date: 28.02.04 19:42 (Sat, 28 Feb 2004 10:42:41 -0800)
From: Joe Huber
Hi Brian

I'd like to compare notes with you, because for me 5.5 makes the
printing behavior consistent across Windows and Mac. Kudos to Aaron

I have a test program that exercises all of this in pretty good
detail and the printer graphic's origin seems to be in the right
place to me. I'll send you a copy off list so we can compare results.

Thanks,
Joe Huber


>I noticed that my app's printing was cut-off at the left and top
>under Win32, and found a note in the release notes saying that there
>was a "Fix" for Win" where the printed area was no longer offset by
>the width and height of the non-printable area.
>
>It is easy enough to reinstate the correct behavior by putting this
>offset in oneself wherever printing occurs but, because the "Fix"
>was only put in for Win32, one has to put in conditional compilation
>in all printing situations. This seems a pity since one remarkable
>feature of REALbasic is that the same project compiles for both
>Win32 and Mac with very little conditional compilation (and what is
>needed generally reflects the differences in the underlying OS
>functionalities, e.g. the need to put in one's own screen buffering
>under Win32).
>
>The "Fix" just makes the printer graphics object's origin the top
>left of the actual page rather than that of the printable area, and
>seems logical enough, but why was it done only for Win32? If the
>cross-platform anomaly is deliberate then the Language Reference
>needs to warn of the difference, but it does not.
>
>Any insights?, b.
>
>- - -
>Unsubscribe or switch delivery mode:
><http://support.realsoftware.com/listmanager/>
>Search the archives of this list here:
><http://support.realsoftware.com/listarchives/lists.html>

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>