[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
U2 conflicts update
- Subject: U2 conflicts update
- From: Myron Gochnauer GOCH@xxxxxxxx
- Date: Fri, 05 Dec 1997 10:15:16 -0400
Robert and Carl suggested a couple of things:
1) Make sure the STACK dlg code's Save/Get 629 contains "BX ooQ2 "
or *nothing at all* . I set it to the former (yes, the proper
XPL coding), but it didn't make any difference.
2) Rename RECALL and WILD in one or the other conflicting sets of code.
I renamed all instances of these two in Tim Baehr's Enhance.set
code (to RECALLE and WILDE). That didn't fix the problem either,
although now both Tim's enhancements such as CDX and recently-
opened-file-recall work properly and many of the SmartSet utilities
seem to work as well (I haven't tried them all yet). But the help
screens for SmartSet (and Reorgniz.u2 as well, if I load it) are
empty.
Myron
Holmgren wrote:
>
> ** 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
> -----------