Macro issue.. bad coding or bug fixed in v2.2? - Protocols

This is a discussion on Macro issue.. bad coding or bug fixed in v2.2? - Protocols ; Current version: k95 2.1.3. Below is the macro in full. Only the beginning and end is of any concern. Its activated while in CONNECT mode. Theres a low percentage chance that when used repeatedly, it'll lock up the client. Specifically: ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Macro issue.. bad coding or bug fixed in v2.2?

  1. Macro issue.. bad coding or bug fixed in v2.2?

    Current version: k95 2.1.3.
    Below is the macro in full. Only the beginning and end is of any concern.
    Its activated while in CONNECT mode.
    Theres a low percentage chance that when used repeatedly, it'll lock up the
    client.

    Specifically:
    Blank black screen in COMMAND mode (ie: cls clears everything) with a
    flashing cursor.
    Ctrl C doesn't work at this point.
    Alt X doesn't work at this point.
    Alt Q will work in closing the client.
    There is no error message.

    Though there is a low percentage chance of this happening, it is used every
    30 seconds give or take. I have 3 people testing it out. Crashes the client
    3-5 times a night.

    Is the coding wrong, or is this related to the bug fix for version 2.2?

    -------------------------------------------------------------------

    SET MOUSE BUTTON 2 NONE CLICK \Kadmc

    define admc {
    CLS
    ECHO
    if ( ( match \fscrnstr(0,0,5) route ) && ( match \fscrnstr(1,0,6) status )
    && ( match \fscrnstr(2,0,4) last ) ) {

    if ( ( >= \v(mousecurx) 0 ) && ( <= \v(mousecurx) 76 ) && ( >= \v(mousecury)
    4 ) && ( <= \v(mousecury) 19 ) ) {

    ASSIGN \%Y \v(mousecury)

    ASSIGN \%E \%Y
    ASSIGN \%F \FEVAL(\%Y+1)
    ASSIGN \%G \FEVAL(\%Y+2)
    ASSIGN \%H \FEVAL(\%Y+3)

    ASSIGN \%A \FLTRIM(\fscrnstr(\%E,1,3))
    ASSIGN \%B \FLTRIM(\fscrnstr(\%F,1,3))
    ASSIGN \%C \FLTRIM(\fscrnstr(\%G,1,3))
    ASSIGN \%D \FLTRIM(\fscrnstr(\%H,1,3))

    OUTPUT D\%A\44\100\%B\44\100\%C\44\100\%D
    }
    ELSE {
    ECHO "Macro isn't used here"
    }
    }

    connect
    }





  2. Re: Macro issue.. bad coding or bug fixed in v2.2?

    Scott Caissie wrote:

    > Though there is a low percentage chance of this happening, it is used every
    > 30 seconds give or take. I have 3 people testing it out. Crashes the client
    > 3-5 times a night.
    >
    > Is the coding wrong, or is this related to the bug fix for version 2.2?


    Scott:

    If the program is crashing, then it is a bug. Properly written programs
    should not crash.

    I don't know if the problem is fixed in my private build.
    I am willing to help people with their issues as long as the time
    involved does not become substantial. Your use of Kermit 95 appears to
    be executing code paths that were not used by previous users. Things
    are breaking. When I was in Columbia's employ I would have had fixes
    to you the following day. Now I don't have time to work on Kermit
    unless my time is paid for. If you would like to have the problem
    fixed, I am available for hire to research the problem and implement
    repairs on an hourly basis.

    Jeffrey Altman

+ Reply to Thread