Properties trigger flow problem

[Perfect Human Interface]

A while back I set my knobs up so that setting the knob label in the properties would also name the (preset) parameter, as a convenience thing. The idea was that it would save me from having to fill in both fields every time I changed or added a knob, but I could set the preset name independently if I needed to.

More recently, I found out that the second case wasn't happening. The problem seems to be that every time the module properties window is opened, it pulls values right through, regardless of whether triggers are being blocked or whatever. Take a look at the screenshot to see what I mean:

PresetLabel.PNG (46.46 KiB) Viewed 13931 times

I've tried all manner of things in between the "Preset" string and the value coming into it from "Label" to control whether or not the string value is being set to the "Label" value, but nothing I've tried works because it always pulls the value through whenever the properties panel is opened again. And note that the "Preset" string needs to be changed directly so that it displays correctly in the properties window, so I can't for instance just put a last switch after "Preset" and "Label" (I'm not sure that would work anyways given how it seemingly ignores trigger flow).

I've already spent too long puzzling over this silly issue, but if anyone else has any ideas how to make this work as intended I would be grateful to hear them.

[MyCo]

I'm not sure what you mean... I've tried it, but I can't reproduce it.

BTW: there was a similar bug to what you describe here in previous FS versions, but it has been fixed long time ago

[Perfect Human Interface]

Bah, I just realized I made a similar topic on this issue 2 months ago.
viewtopic.php?f=2&t=3385
And I remember it wouldn't work the same after I tried to recreate it. I think I was using the modules in a different project that time though and having the problem.

BTW: there was a similar bug to what you describe here in previous FS versions, but it has been fixed long time ago

I'm still using 3.0.4. Is that far enough back? (I don't mean to complain, but there's been no indication I know of that serious issues introduced in subsequent updates were fixed at some point.)

[MyCo]

It was fixed in 3.0.1 :

Boolean properties were incorrectly sending a trigger when the properties were opened

So it was only related to boolean. But as I said, can't reproduce your problem... so neither would Malc see it and possibly fix it.

[Perfect Human Interface]

Indeed, I can only reproduce this in (so far) 2 of my projects. Any other instances of Flowstone this doesn't happen.

This alone is enough to demonstrate:

Properties Bug.PNG (5.48 KiB) Viewed 13888 times

Again, simply opening the properties panel causes the second string to be set to the first, and only within these projects.

[MyCo]

Again, I can not reproduce that.
How about posting a schematic and a step by step walk through to see the problem?

[Perfect Human Interface]

Again, I can not reproduce that.

Sorry, that's what I'm trying to get across... I can't reproduce it either. I can only reproduce it within these specific schematics.

I'm trying to find a way to upload something to demonstrate (aside from uploading my whole project), and I'm finding it starts happening somewhat sporadically (e.g. it won't happen immediately after loading but after clicking around between modules for a bit it will start). I've created a module (exactly as above) in one of these projects, and I've found that I can delete everything else in the schematic and it will still happen, but if I then save and reload the project it ceases, so uploading it won't do any good.

I appreciate you taking the time MyCo, but I think the only chance of demonstrating it would be to upload my entire project, which in this case I can't do publicly. But even if that did work, I'm not sure if it would be much help, seeing as it's in a big messy project and therefore it's still not clear how to reproduce it exactly.

Edit:
Like I mentioned above, it seems to not happen when I first open the project, but after clicking around in the project for a while it will start. I've found I can also just click to open and close the properties window over and over again until I see it happen as well. So for some reason the clicking/interacting within the schematic eventually causes it to start happening.

The following numbers (from loading the project and then opening and closing the properties window until I see it first happen) don't seem to mean anything in and of themselves but just show how sporadic it is:
The first time I did it it took 10 tries. The second time it took 30 tries. The third time it took 5 tries. The fourth time it took 20 tries. The fifth time I tried it it took 120 tries (sic). The sixth time took 34 tries (So I guess it's not always divisible by 5 after all, hah). And the seventh time took 32 tries.

Again, this is only in this schematic. I cannot reproduce this elsewhere. I've tried clicking many times.

[RJHollins]

Does this only happen when using a 'Wireless' link to connect the param name ??

[MyCo]

in your "big" schematic, try that:
Connect a "Trigger Counter" parallel to the 2nd input... and then open/close the properties til the 2nd input changes. Now go back to the Trigger counter and look if it increased. Basically you'll see if there was a real trigger or if it just was a backward value re-read.
In case of the last, you could work around that with a "sample and hold" with both inputs connected to the first input. If it's a real trigger, there is no chance

[Perfect Human Interface]

Does this only happen when using a 'Wireless' link to connect the param name ??

No, it has nothing to do with the wireless. Myco's last example schematic is exactly what I'm working with.

in your "big" schematic, try that:
Connect a "Trigger Counter" parallel to the 2nd input... and then open/close the properties til the 2nd input changes. Now go back to the Trigger counter and look if it increased. Basically you'll see if there was a real trigger or if it just was a backward value re-read.
In case of the last, you could work around that with a "sample and hold" with both inputs connected to the first input. If it's a real trigger, there is no chance

It isn't a trigger. I realized this when I wired up output strings like you had and the value didn't propagate out to them. And I verified with the trigger counter just now as well.

I don't quite understand your suggestion though. Of course two strings wired to one input will combine them.
If you mean something like in this pic, I've tested it and it still happens.

Properties Bug 2.PNG (10.59 KiB) Viewed 13870 times

If it actually was a trigger I could just switch it with a trigger switch or something and my previous confused attempts to thwart this would not have been in vain!