| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 365.1 | Use Set for Show | COOKIE::KITTELL | Richard - Architected Info Mgmt | Sun Sep 30 1990 14:13 | 13 |
|
But then I noticed that I *can* select the text from fields in the Set
window. And that by selecting Show Current Values in the Set window, it
effectively does a Show.
Is there anything a Show window can do that a Set window can't?
Also, what is the trick to get Show Current Value.. and Show Value For..
to work? They always complain that no field is selected, but I've got the
pushbutton on and have clicked in the field to bold the I-bar.
What is the functional difference between Show Current Value.. and
Show Value For..?
|
| 365.2 | | VERNA::V_GILBERT | | Mon Oct 01 1990 12:50 | 28 |
| Richard,
You are correct - no cut and paste for the first release.
However, as you noticed, Show Current Value
Show Current Values
Show Value For...
Show Values For...
all allow you to "show".
I do not understand why Show Current Value/Show Value For do not work for you.
I tried them on the V1.1 IFT kit and had no difficulty doing the following:
select a text widget in a set form by pressing MB1 over widget
(I-bar gets highlighted)
select Show Current Value from the Edit Menu
The difference between Show Current Value and Show Value For is:
In the first case a show is done on the entity for which the set form is
displayed. In the second case, the user must enter an entity instance (which
must be in the same domain as is the entity for the set - the domain name will
be displayed in the Management Window for EFT).
A Show window is the only way to see the attributes in a partition which has
no settable attributes. Otherwise the above menu items do allow you to do
a show in a set form.
Verna
|
| 365.3 | Still can't Show Current Value | COOKIE::KITTELL | Richard - Architected Info Mgmt | Wed Oct 17 1990 12:57 | 13 |
|
RE: .2
Verna,
Thanks for the info, that cleared up my questions nicely.
But I tried again just to be sure, and still get an error from Show Current
Value. It thinks no field is selected even though the I-bar is bold in
one of the fields.
If you want to see, copy COOKIE::AIM$PUBLIC:[ETC]MCC_NOTE_365.DDIF and have
a look at it, perhaps there is something else at work.
|
| 365.4 | | VERNA::V_GILBERT | | Wed Oct 17 1990 15:19 | 7 |
| Richard,
As I previously mentioned, I cannot duplicate the behavior you describe re.
Show Current Value. Is there any way I can log onto your system and set
the display back to mine so I can see what is happening.
Verna
|
| 365.5 | CLOSE TOPIC: Beware AutoFocus | COOKIE::KITTELL | Richard - Architected Info Mgmt | Wed Oct 17 1990 18:16 | 24 |
|
RE: .4
Verna and I worked on this problem over the phone and network, and the trouble
was in my environment.
I run a utility called autofocus on my Ultrix workstation. This causes the
DECwindows focus to follow the pointer: instead of having to click to get
focus in a window I just move the pointer into it. Among other advantages,
this lets you type into a window without pulling it to the top of the
stack.
When trying to use Show Current Value, pulling down the operations menu
causes the field to lose focus, because autofocus moves the focus to the
menu window. So by the time the Show Current Value command executes,
none of the attributes have focus anymore.
Solution: Don't run autofocus if you want to use the Show Current Value
feature of the Set window.
I'll change the title of the basenote, since this has expanded to more
than Cut and Paste.
Thanks Verna, for the house call.
|