| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi, I have an entity structure (part of) that looks like the following: ALARM_CLASS (has variants) | ALARM (doesn't have variants) The IMPM displays the following: [ALARM_CLASS ...] [ALARM_CLASS 4] [ALARM_CLASS 3] [ALARM_CLASS 2] [ALARM_CLASS 1] [ALARM_CLASS 0] When I double click into the ALARM_CLASS 0 entity instance it appears that the IMPM calls the following entry-points in my AM : calls SHOW ALARM_CLASS 0 ALL CHAR [ now displays message "looking into ALARM_CLASS 0" ] calls SHOW ALARM_CLASS 0 ALL CHAR calls SHOW ALARM_CLASS 0 ALL CHAR The the IMPM displays the following: [ALARM...] When I double click into ALARM ... entity class it appears that the IMPM calls the following entry-points in my AM: [ now displays message "looking into ALARM ..." ] calls SHOW ALARM * ALL IDENT My question is: why does the IMPM issue the SHOW ALARM_CLASS 0 ALL CHAR directive three times ? Ok, when it displays [ALARM...] the Operations menu is still valid for the ALARM_CLASS 0 entity instance so it has to find the contents of the Operations menu because this depends on the variant. So one call of the SHOW ALARM_CLASS 0 ALL CHAR directive is explained, but the other two ?? Why is the directive issued before the IMPM displays the "looking into" message ??? Is this not a little overdue ? Regards, Paul Goes
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2380.1 | QAR 2386 | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Wed Feb 26 1992 13:09 | 2 |
QAR 2386 | |||||
| 2380.2 | re:.1 | BARREL::LEMMON | Wed Feb 26 1992 14:47 | 12 | |
The iconic map uses the Gobe widget. The doubleclick actually is two
single clicks and gobe checks to see if the x,y coords are the same.
If so, it calls the doubleclick callback.
A side effect of this is that the single click callback is invoked
for each click before gobe knows that the user really meant to double
click. This could be optimized but noone has noticed a problem with
performance so we focused on other areas.
/Jim
| |||||