[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: framers <framers@xxxxxxxxxxxxxx>, Free Framers <framers@xxxxxxxxx>
Subject: macro and menu command failure
From: ERIC Lawson - x52010 <eric@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 28 Mar 2000 15:18:26 -0800 (PST)
Sender: owner-framers@xxxxxxxxx
Using FM 5.5.6 on a Solaris system, I attempted to create a macro that would surround a text selection with two custom marker types, one at each end. Both markers are empty. First I tried building the macro with the standard keystrokes: <Definition \!ex\!Fim+/Tab \s0/Up /Up /Up \s/Tab /Tab /Return \!Fid\!ep \!Fim+/Tab \s0/Up /Up \s/Tab /Tab /Return \!Fid> <Mode NonMath>> These keystrokes do the trick when not invoked as a macro. When invoked as a macro, the macro exits without generating an error message after the first marker is inserted and the focus is returned to the document (<Definition \!ex\!Fim+/Tab \s0/Up /Up /Up \s/Tab /Tab /Return \!Fid). I next attempted to build the macro as the corresponding set of fcodes in a menu command. This attempt had the same result in that the menu command bombed at the same point upon execution. Can anybody help explain this FM macro (and Command) behavior, or suggest another procedure that will work to the same end? My own investigations suggested that the problem resided in variable treatment of modal and modeless dialogs in macro and command execution...but that didn't suggest a solution to me. regards, Eric James Eric Lawson Research Publications Editor III National Simulation Resource eric@bioeng.washington.edu ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **