Re: U2 conflicts?

[Robert Holmgren holmgren@xxxxxxxx]

** Reply to note from xywrite@xxxxxxxx Thu, 04 Dec 1997 14:04:22 -0400

Myron, I assume when you refer to "rewritten" commands that you are using
the features that XyQuest calls "Command Customization" and "Command Override"?

If so:
CAll STACK.DLG (or the larger .DLG file such as XY4.DLG into which the Stack code
is merged). SEarch for frame {{5stack.int}}. After LaBel C , make sure that
Save/Get 629 contains "BX ooQ2 " or *nothing at all* (you can just copy
this code from User Variable note C, one screen or so earlier in the file -- read
that note to determine what STACK thinks your current default is, and what it means
when you change S/G 629 -- I don't have ENHANCE.SET, and I don't know what it
does, but if it redefines standard factory-issue commands -- acceptable maybe in a
single workplace with lots of single-minded workstations, but a TERRIBLE idea in
public programming, I think -- then you MUST use the "BX ooQ2 " code). Reload
this modified DLG file, issue "oo" on the CMline to re-enable Command
Customization, and you should be off and running. It sounds to me like Stack was
turning off Command Override (its default method of operation). If you want to know
the rationale for this, read STACK.DOC, "Step TWO Customization Information",
paragraph #3.

Let me know if this fixes your problem. If not, hmmm... What is ENHANCE.SET?
Never heard of it.


-----------
Robert Holmgren
holmgren@xxxxxxxx
-----------