Recalcitrance indicates some degree of difficulty to control, unwillingness to obey requests or directions, uncertainty in behavior.
And that’s exactly what the Lotus Notes properties box used to be, whether used in the Lotus Notes client (for end-user activities, such as setting text properties like font size and color) or in the Domino Designer client (for setting all sorts of properties for a wide range of object types, such as fields in forms or view column properties).
Alan Lepofsky in his LepoLand blog has quite a few good basic and advanced tips about using the Notes properties box. This search link should list most of his tips.
Now let me ask you a question. What’s the important distinction between the dispositions of the following two Lotus Notes properties boxes?
|
|
|
Did you work it out? Probably not, I suspect.
The one on the left is what happens up to and including Notes 7.x if you have multiple monitors and attempt to drag the properties box to a secondary monitor configured to lie on the right of the primary monitor (number 4 in the image below). The box only moves half way into the secondary monitor area and then gets stuck, half in the primary monitor and half in the secondary one. … Yoiks!
The image on the right shows what you get for Notes 8. Well, for Notes 8.5 at least, I can’t verify that this also happens for Notes 8.0 because I don’t have it installed any more. Three cheers, at last this usability glitch has been done away with. It’s about time, but better late than never, so thank you IBM! Now
These days I happen to use four 20-inch Samsung LCD monitors of 1600 x 1200 resolution arranged in an inverted T configuration (enjoying glorious high-resolution wallpapers, such as the panda, from Webshots).
Yes, I’ve spoiled myself, but that’s at least one benefit flowing from being self-employed.
When doing really intense application design work with Domino Designer, I find it incredibly efficient to have three or more designer panes open at once (for form design, view design, coding, etc) all laid out in their full individual glory on separate monitors. It’s really effective for side-by-side display of, say, two form or view designs, or two LotusScript subroutines.
I can also rotate any of the screens to portrait-mode position, such as when I spent almost two weeks carefully rewriting the NotesTracker Guide.
Errant behavior like the above is far more commonplace than it should be. I find the native Windows XP/Vista support of multiple monitors to be excellent. You can position your two (or three, or four, or more) monitors in various positions relative to each other, and Windows handles it all with aplomb. When you rotate a monitor, Windows handles this flawlessly too. Splendid work by Microsoft!
Unfortunately there are quite a few applications out there in the wild that don’t correctly handle multiple monitors. Some refuse to work on any but the primary monitor. Others do bizarre things, such as always opening in a particular secondary monitor, or opening spread across all of the monitors as if they were a single huge monitor. This is just poor application design and/or coding. I’d hate to see such really unreliable work done for things like airplane control or nuclear power station operation. (Maybe it is, in small ways?)
Over nearly forty years in the industry, I’ve noticed that there aren’t all that many many employers willing to provide their IT staff with much more than basic hardware (or software, for that matter). More’s the pity, since these days items like good quality high-resolution LCD monitors and well-endowed desktop/notebook PCs are quite inexpensive and are IMHO essential productivity tools to give to power developers (and administrators).
0 comments:
Post a Comment