Re: closing a macro completely upon connect

On 2006-03-09, Scott Caissie <scottac@xxxxxxxxxxxxxxx> wrote:
: ya but unfortunatly our terminal emulation is leased. I have to make due
: with whats avialable to us as is.
: We have no administrator within the company for this software. I'm the only
: one who actually bothered to research this stuff. I've developed many
: improvements. But some I have to put on hold due to that. Normally all bug
: fixes are free. Enhancements cost. This unique situation would involve us
: paying this company to pay for the fix. And they are already behind on a lot
: of bug fixes of their own.
:
Bug fixes AND upgrades were free from the very beginning up until the layoffs
occurred 3 years ago. The problem now is that the expertise is no longer
under one roof. At least the critical fixes *are* available, albeit at a
fee.

: But back on topic, how to properly deal with a macro from becoming nested
: too much.
:
I don't think there is a workaround to the "macros on keys" bug, other than
the awkward one mentioned in the bug list:

735. Macros on Keys broken

In versions 1.1.21 through 2.1.3, when a SET [TERMINAL] KEY definition
includes a macro invocation, then pressing the key while in the
Terminal screen returns to the command screen (and in some cases might
also fail to execute the macro). A workaround would be to:

define myconnect connect /synchronous
(make the connection with SET PORT, DIAL, or SET HOST)
if success do myconnect

This is fixed in the next release.

As I said, I'm working on getting approval to issue a new release.

- Frank
.

Relevant Pages

  • Re: closing a macro completely upon connect
    ... "Normally all bug fixes are free. ... would involve us paying this company to pay for the fix. ... how to properly deal with a macro from becoming ... I don't think there is a workaround to the "macros on keys" bug, ...
    (comp.protocols.kermit.misc)
  • Re: FindFirstFile, how much faster than FindNextFile?
    ... >>so the whole discussion about whether a switch statement is ... The time to find a bug is not when you are using it. ... Not Another Macro Recorder! ...
    (microsoft.public.vc.mfc)
  • Re: Word 2003 resetting default printer
    ... If it is a bug, I had not come across it. ... Microsoft' via this forum will achieve anything. ... ActivePrinter command to point to the correct default printer in an autoopen ... and autonew macro in the document template or normal.dot in your profile. ...
    (microsoft.public.word.docmanagement)
  • Re: MoveRight in table fails at 1%: bug? workaround?
    ... temporary files as your macro runs, so that all changes can be undone. ... about erros at Selection.MoveRight command? ... >> Does anyone know something like a known bug about MoveRight? ... Using the Selection object makes for more convoluted ...
    (microsoft.public.word.vba.general)
  • Re: Why I believe in static analysis
    ... > However, we only applied them to part of the codebase, and the bug ... the SPIN users happened to translate the Lisp code ... control over the built in monitor locks. ... they also might have been avoided by using such a macro to abstract ...
    (comp.lang.lisp)