> [mailto:[EMAIL PROTECTED]]On Behalf Of Mats Elfstr�m
> Sent: March 13, 1999 5:50 AM
> Subject: Re: MI Determining screen res / writing resolution independant
progs

> Well, there is always the possibility to query the system metrics, and
> indeed,  such solutions has been posted to this list. And they work.
> However, knowing screen resolution is not enough.
>
> The real question is: how much screen space is available in MapInfo for
> the windows of my application?
> This space is of course dependant on a number of factors, namely:
>
> How big is the MI window, is it fullscreen or not?
> How many Toolbars are open and docked, how wide is the toolbar at the op?
> Does the user have a status bar at the bottom?
> Which is the width of the window borders?
>
> Funny enuogh, all this must be known to the MapInfo kernel, in order to
> tile windows.
> Would it be impossible to dig out this info with a MB function, for
> example
........

This may be a partial answer ot the query. It may be also a bit lengthy, but
traffic on the weekend is at a low level and it will give you a nice feeling
to drop it first thing Monday morning to clear your mail box. It is part of
a text I have started to write on the subject of WMF export from MI, and it
may be a way to put it to the test.

============

1 - 0  MI document window size

The window size that can be set in MapInfo MI has some lower and upper
limits. As these depend on the particular installation display
characteristics, exact dimensions cannot be given here.

To have a good idea of the maximum values, within 5/100 of an inch, use the
MapBasic window. Type and run

        Print windowinfo(1011,4)
        Print windowinfo(1011,5)

to get the width 4) and the height (5) in the current paper units (inches by
default). If you prefer metric dimensions, type and run in the MB window
before the previous commands :

        Set paper units "cm"

To get a more complete information, use the free utility WINDOSIZ.mbx
(available on http://www.total.net/~rparis/gisproducts.htm). Make a mapper
the active window, run the utility by setting width and height to large
values (say twice the dimensions obtained in the previous test). Run the
utility again and record the "actual" dimensions of the window. Change its
size to very small values (say 1/10 in or 1 cm), run the utility again and
record the "actual" dimensions of the reduced window.

The maximum size is the most important because it tells you what could be
the maximum size of the exported image. The size of WMF files does not grow
with the size of the exported window, which is not the case with bitmaps,
thus larger windows are not a handicap. Besides, one may find easier to work
with the largest window as possible.

Maximum window size is that of a window that would be "Maximized". If it is
not maximized but set at its maximum size, such a window will extend outside
the MI main window and it will be necessary to use the scroll bars to view
the hidden parts of the mapper. That a window extends beyond the MI main
window may give the impression that there is no limit to the maximum size.
That is not so; the actual maximum is the same, whether the document image
is fully or not within the MI main window.

Window size includes the scroll bars if they exist as an option in that
window type. To really see all the contents of a mapper window, it is
recommended to remove existing scroll bars. Scroll bars are a set feature of
the browser and layout windows but do not exist in a grapher.

=======================

Jacques Paris
============================================================
e-mail        [EMAIL PROTECTED]

gis activity (MapInfo mainly)
      http://www.total.net/~rparis/gisproducts.htm
============================================================

----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]

Reply via email to