Refresh GUI


    Sep 19 2006 | 11:53 am
    Dear all, I've some problem refreshing the graphical interface when I create and delete a bpatcher using javascripts. I'm simply using something like:
    patcher.remove(mybpatcher);
    but I can actually see that object is eliminated only if I switch in edit mode and go back to no-edit mode again.
    Does it exist a "patcher.refresh()" method or something? (similarly to the "refresh()" method in JSUI I guess).
    Thank you, Bruno
    ------------------------------------------------- - http://www.brunozamborlin.com - -------------------------------------------------

    • Sep 19 2006 | 12:41 pm
      On 19 sept. 06, at 13:53, Bruno Zamborlin wrote:
      > Does it exist a "patcher.refresh()" method or something? > (similarly to the "refresh()" method in JSUI I guess).
      did you try max.refresh()? It should do it.
      Best, ej
    • Sep 19 2006 | 1:26 pm
      loadbang offset x x thispatcher should also update the display of a newly scripted bpatcher
    • Sep 19 2006 | 1:34 pm
      > did you try max.refresh()? It should do it.
      It works great, thanks!
      Bruno
      ------------------------------------------------- - http://www.brunozamborlin.com - -------------------------------------------------
    • Sep 19 2006 | 2:16 pm
      seq in 4.5.7. on 10.3.9:
      from the max reference: dump Opens a standard Open Document dialog box, to select a saved sequence or standard MIDI file. The selected file is opened as text in a new Untitled text window, which can be edited and saved.
      doesnt work here with MIDI file: tested with several midifiles (exported patterns from live5) that all work with "read". "dump" -> select file.mid -> seq opens an empty window, nothing happens
      doesnt work here with "a saved sequence": i saved the sequence from the reference 0 144 60 112 1000 144 60 0 1500 192 31 1500 144 60 112 2500 144 60 0
      as: seqtest, seqtest.txt, seqtest.mid
      "dump" doesnt even allow me to select seqtest or seqtest.txt. "dump" accepts seqtest.mid but opens an empty window (see above)
      --------------------
      from the max reference: read With no arguments, read calls up the standard Open Document dialog box, so that a previously recorded sequence can be read into seq
      read seqtest read seqtest.txt read seqtest.mid
      all give me the same error: "bad midi file (truncated)"
      best p
    • Sep 19 2006 | 5:49 pm
      Hello, This is a known bug, and will be fixed in the next update.
      Cheers, Andrew B.
    • Sep 19 2006 | 10:11 pm
      thanks!
      so i guess this one is also known:
      bang Out right outlet: Indicates that seq has finished playing the current sequence. (The bang is sent out immediately before the final event of the sequence is played.)
      when printing left and right outlet of seq it shows that the bang is sent out immediately AFTER the final event
      i would like to add some feature request: some command that lets one retrieve the duration of the loaded midifile / sending out the fileduration the 2nd outlet as integer after finished loading. some sort of loop function based on bars/beats.
      best p
      Andrew Benson wrote: > Hello, > This is a known bug, and will be fixed in the next update. > > Cheers, > Andrew B. > >