@freq63 said:

What I find confusing is the fact that all 4 values are printed without issue separately before unpack.

separately is the word. [unpack] get the values one (two) after each other so only its (two) first inlet(s) is (are) triggered.

The messages come one by one (or two by two) so the unpack never get a 4 items list.

You can accumulate the messages to 4 this way:

This is your triggerized patch:

You can see the right branch is triggered before the top-most [t f f] feeds the [pack] so the numbers are all generated by the loop before they was printed.
EDIT: you stack computation branch and they are released deepest to shallowest so numbers are reverted.

1. Do not split the control flow without [trigger]
2. Why don't you use [until] ?

I think it's easier to dynamically upgrade the variable name with the [list prepend] right inlet.

[netsend] help for the [send( message says "same as list" so you can also do

[hslider]
|
[list prepend z]
|
[netsend]

Simply connect the slider to the sender.

@fishcrystals said:

//these magic functions let us send human readable info to pure data
void fudiStart(){
  Serial.write(108); //Fudi
  Serial.write(105); //Fudi
  Serial.write(115); //Fudi
  Serial.write(116); //Fudi
  Serial.write(32);  //Fudi
}
void fudiEnd(){
  Serial.write(59);  //Fudi
  Serial.write(10);  //Fudi
}

Could be:

//these magic functions let us send human readable info to pure data
void fudiStart(){
  Serial.print("list ");
}
void fudiEnd(){
  Serial.print(" ;");
}

and become not-so-magic…

@jameslo If you have to restart the phasor at the state it stops you can follow your first idea and stop it at a specified moment, save the state and later restore and relaunch. What I propose is to only allow the phasor to stop at specific states (e.g. every 0.0001) so it's easier to save. When the stop is required the phasor will wait to reach an allowed state and then stop. So the stop time is fuzzy but the state is clear and clean.

I've no idea if and how it can be implemented or if it follow your requirement.

If you can't know the state of the phasor at a given stop time maybe you can stop it at a specified state and so transfer the incertitude to the stop time. It can be a solution, depending on what you need.

Another possibility with [list]:

Update:

• Add an "update" message to redraw the text without the need to hide/show. You can display info in real time.
• Fix a bug where the tip is not shown until you switch the edit mode
• Add a position offset so the text is less under the cursor
• Clean the patch

Hi,
my exploration of the iemguts library bring me this idea:

tooltip.zip

Enjoy!

OK got it: setting the "gop mode" to zero is not enough, it has to be set with the large dimensions and then it can be shrink without ghosts.

And then it works with [coords( too.

EDIT: I've fixed it with a list:

@oid not better

@oid even with the minimal test

EDIT:
I can force the redraw with

[zoom 2, zoom 1(
|
[sendcanvas]

@oid this simple test doesn't work so it's certainly a bug with my system.

I have another issue with comments:

And [donecanvasdialog( is worse: all the guis remain visible as ghosts.

@oid A realtime on expr indicates a 8ms compute time. I'll try with your version.

I've added a change and a pipe to delay the switch.

It doesn't fix the comments problem, they only disappear when I save their containing abstraction (or when I reload the main patch).

Now I'm looking for a dynamically added and resized background canvas to get rid of the transparency.

@oid my bad, I wasn't clear enough.
I've done what I mind:

makeExpandable.pd

I've an issue with comments which remain visible when the gop is shrunk.

I'd like to put this whole logic in an abstraction so I'll can reuse it but I don't find how to sendcanvas
to the parent patch