| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2518.1 | | STAR::VATNE | Peter Vatne, VMS Development | Tue Mar 27 1990 12:54 | 7 |
| > What "comes" with DECwindows? Can a third-party depend
> a certain set of fonts being on the system?
The list of fonts provided with DECwindows is in Appendix D of the
Guide to Xlib Programming. They may count on all or none of the 75
DPI fonts existing, and all or none of the 100 DPI fonts existing,
depending upon how the user tailored the system.
|
| 2518.2 | So what if no fonts are there? | ESRAD::PANGAKIS | Tara Pangakis DTN 287-3551 | Mon Apr 02 1990 13:18 | 4 |
| re: .1
So if none of the fonts are guaranteed to be there, what do
applications do?
|
| 2518.3 | Wildcard the resolution field | STAR::VATNE | Peter Vatne, VMS Development | Mon Apr 02 1990 14:02 | 12 |
| Well, if the user tailored off ALL the fonts, then of course the program
has no choice but to print an error message and die. However, that is
an exceptional case. The application writer can count on at least one
set of fonts (either 75 or 100 DPI) to be there.
I'm not sure yet what the best way is to handle resolutions. However,
most of the applications I've observed wildcard the resolution field.
This will pick up either resolution, depending upon which was tailored
on. If both were tailored on, it will pick up the first resolution
in the default font path. The first resolution in the font path is
normally 75 DPI, although this can be overridden in SYS$STARTUP:
DECW$PRIVATE_SERVER_SETUP.COM.
|
| 2518.4 | Recommendation: Don't wildcard OpenFont | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Tue Apr 03 1990 15:06 | 11 |
| BTW, you would be better off doing a ListFont with the resolution field wild
carded to save you grief in the long run. Wild carding open font could
cause trouble in the future with scalable fonts.
Wildcards with openfont was a DEC invention which we rammed down the throats
of an unwilling consortium. No one else uses it much and people won't feel
too sorry if future conventions make it not work.
A word to the wise...
Burns
|
| 2518.5 | International guidelines? | ESRAD::PANGAKIS | Tara Pangakis DTN 287-3551 | Tue Apr 24 1990 16:25 | 2 |
| Is there such a thing as a "DECwindows Developers Guide to Developing
International" applications?
|
| 2518.6 | | BBOOP::SCAER | | Wed Apr 25 1990 13:27 | 5 |
|
RE: .5
The set of manuals is called the "Producing
International Products" reference set.
|
| 2518.7 | How can one inquire for screen resolution? | EPIK::MJDAILEY | Mike Dailey; ZKO2-2/M28 | Wed Oct 24 1990 13:02 | 5 |
| RE .4
Is there any way to detect the display system's screen resolution in dpi?
Mike
|
| 2518.8 | | IO::MCCARTNEY | James T. McCartney III - DTN 381-2244 ZK02-2/N24 | Wed Oct 24 1990 14:49 | 11 |
| RE: .-1,
Give a widget id from the toolkit, you can do the following:
horiz_dpi = XDisplayWidth(XtDisplay(w),XtScreen(w)) /
XDisplayWidth(XtDisplay(w),XtScreen(w)) / 25.4;
vert_dpi = XDisplayHeight(XtDisplay(w),XtScreen(w)) /
XDisplayHeight(XtDisplay(w),XtScreen(w)) / 25.4;
James
|
| 2518.9 | Typos | GVRIEL::SCHOELLER | Schoeller - Failed Xperiment | Wed Oct 24 1990 15:49 | 10 |
| .-1
those should be
XDisplayWidth () / (XDisplayWidthMM () / 25.4)
and
XDisplayHeight () / (XDisplayHeightMM () / 25.4)
Dick
|