LoadCue w/Format in Blind Spreadsheet

In the eos offline editor, when I go to Blind Spreadsheet mode and press F4 (Format), the system locks up.  The Clear (backspace) key will not erase the command line and pressing F2 (Live) causes the command line to display "LoadCue" followed by the cue number on the spreadsheet.  The F3 (Blind) key does not do anything, nor does F4.  I searched the manual for "LoadCue" but found nothing.   I found a couple of instances of "load cue" with a space, but not a command.  The "Q" key also has no effect.  If I exit and restart, it cleans up the problem. 

What did I do wrong and how do I undo it without exiting?

Parents
  • I just tried to replicate this on my home machine, a Win 7 Home unit, running OLE 2.1.2.

    Not seeing any of these issues here.

  • I've played with it some more.  It's related to the keyboard.  The VK works, but the many of the keys on the keyboard are non functional.  F2 causes "LoadCue" to appear in the command line.  bksp doesn't clear it, though it will clear some other command line entries.  It's as though the keyboard has been placed in some weird state.  It happens on two machines, so it's not hardware related. 

    Playing some more, it is behaving as though the control key is being held down for every keypress.

    1 = Snapshot
    2 = LoadCue
    3 = {stop/back?}
    4 = macro
    5-0 = Encoder
    B = beam
    I = intensity
    etc.

    It is only doing this for OLE, not any other programs on the machine.

     

  • I've narrowed it down a little more with some additional experimentation.  I cleared my show and the problem went away.  No surprise, I had begun to suspect it must be related to the show file.  I then merged my magic sheet into the blank show and the problem came back.  Something about my magic sheet causes this problem.  Since I cant export the magic sheet to USITT, is there a way to look at it to see what might cause the problem?  I have an uncanny knack to break things like this.  I guess I push everything to the limit.

     

Reply
  • I've narrowed it down a little more with some additional experimentation.  I cleared my show and the problem went away.  No surprise, I had begun to suspect it must be related to the show file.  I then merged my magic sheet into the blank show and the problem came back.  Something about my magic sheet causes this problem.  Since I cant export the magic sheet to USITT, is there a way to look at it to see what might cause the problem?  I have an uncanny knack to break things like this.  I guess I push everything to the limit.

     

Children
Related