| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I have a couple of strangies to inquire...
(1) I have a Firefox (3520) with the Vr295 monitor. When I use X to
query the device for pixel sizes and info, I get the same data that
the VR290 reports, even though the pixel/CM is much finer on the
295. Also, I receive many "...Error event received from server"
messages from some of my own applications when I try to display
remotely from/to 3520.
(2) I have a work area with a Attached DB on top of the work area.
Then I have another ADB with an X Window on top of it. I use
the X Window to display graphics, and the ADB behind it for
mapping the MB2 hit to a popup-menu. Now here is the strange
behavior: On different platforms, PMAX, MVII, 3500, 3520, 3100
I receive different events when using this scheme. My popup-menu
has a "zoom" button. When selected, I perform a "rubber box"
until the user presses MB1. Now the code works fine. Then I
added an optimization, when I "Leave" the X Window I want to
"shut down" the zoom. So I just check for a LeaveNotify on the
window. OK - I receive a LeaveNotify on the window when I
press MB2. I understand that. What confuses me is this: I
select zoom and move my cursor around WITHIN the window. It
works great. Then when I press MB1 I eventually receive a
ButtonPress event. However, on some platforms I first receive
a LeaveNotify event. I added a check to only cancel my zoom
if the mode is NotifyNormal. This works for me, but I am not
sure that I fully understand why.
Christopher
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2157.1 | dpi setup info | DECWIN::BMATTHEWS | Mon Jan 29 1990 10:34 | 13 | |
For part 1 use the sys$manager:decw$private_server_setup.template file to create a .com file that requests a 100 dpi set up. When firefox came out there were a significant number of apps that didn't handle 100 dpi systems so the default for all systems even firefox is 75 dpi. The server software has no real way of determining the density of the monitor that is attached to the workstation. Also, we report back the monitor size such that the monitor appears to be either exactly 75 or exactly 100 dpi so that apps can have there graphics drawing match the fonts they use. For example if we reported back that the monitor was 95 dpi and the app wild carded the font to get 100 dpi font then intermixed graphics and text may not agree on placement and cause lot's of problems for the apps. Bill | |||||
| 2157.2 | Time passed, issue remains... | VMSDEV::KALER | Mon Apr 02 1990 15:20 | 24 | |
Well, since I wrote this note I have left the group. I decided,
however, that the topic should be continued. The problem that the
software is having is that the user requests a window that is to
be 3 by 4 centimeters. The software uses a device query to obtain the
pixels per centimeter and then multiples to get pixels for DecW/X.
Now, in the Firefox a 10cm line is NOT 10cm. I understand all that
you have told me, but as a DecW user, I expect to be able to determine
the exact resolution of the monitor. They also did try changing the
private setup to be 100 dpi, the size were closer, not perfect, but
many applications like decw$mail and notes starting having some "odd"
font choices. This I belive is the behaivoral you reffered to.
Now, it seems that someone must provide and middle ground. It is not
unreasonable for the application to request the actual device
resolution or to ask for the "closest" font dpi. UIS provided this
form of device query (for resolution).
Fell free to contact me off-line at VMSDEV::KALER.
Regards,
Christopher
| |||||
| 2157.3 | STAR::KLEINSORGE | Fred Kleinsorge, VMS Development | Tue Apr 03 1990 11:33 | 15 | |
UIS didn't do that swift of a job in that regard. It's font selection
mechanism was poorly designed from a resolution independence point of
view. The XLFD mechanism, if somewhat wordy, *does* allow you to
wildcard the font resolution and pick a physical size. So a properly
written application should work. If applications that we can assume
are done right are not working - check to see if you've customized a
hardwired font selection into it's resource file.
(BTW - also think you should be able to ask what the resolution
"really" is - for applications that want the physical size *exactly*
the same across all monitors.)
_Fred
| |||||