T.R | Title | User | Personal Name | Date | Lines |
---|
2141.1 | We've seen it too (+workaround) | HLRG02::GOES | | Mon Jan 20 1992 12:02 | 23 |
| Hi,
We have seen it too and have a little 'dirty' workaround for it:
If you drag your icon to the border of the mapwindow and you keep 'pushing',
you can make your window shift into the 'hidden' area.
This sounds strange but if you drag icons to the border and you release
MB1 when the icon can't be moved any further the window shifts a little. It
is then possible to drag the icon a little further and the windows shifts
again. Try this many times and it looks like you are 'pushing' the window.
By doing this you can make all parts of the map visible.
If you have everything visible you can draw a very small (almost invisible)
line at the border of the map.
Now you can save the map and if you open it again it will place the
very small line at the border of the window (or a little outside the
window (but who cares about the invisible line ?) ) and the remainder
of your map is visible !
Regards Paul Goes & Henk van Steeg
|
2141.2 | I've seen it also | NSCRUE::KEANE | U.S. NIS Service Development and Delivery | Mon Jan 20 1992 13:19 | 7 |
|
I've seen this also, and what I have been using as a work around is to view
rules and then return to view members. If I remember correctly this was a
problem during V1.1 field test also.
Scott
|
2141.3 | QAR 2167 | TOOK::MINTZ | Erik Mintz, DECmcc Development | Mon Jan 20 1992 13:36 | 3 |
| Entered as QAR 2167 (for the autoconfig component, although
it may be re-directed to the IMPM)
|
2141.4 | will be fixed | TOOK::R_SPENCE | Nets don't fail me now... | Fri Jan 31 1992 19:59 | 5 |
| I believe this is fixed for the next available kit. I qared it early
in field test myself. Eric, see qar 1866.
s/rob
|