Module not staying in Toolbox: WTF?

[tulamide]

Write permission doesn't act selectively. If you can add other modules to your toolbox, you have the rights. Also, I was relying on PHI's comment that he didn't have any issues. I shouldn't.
Just downloaded your schematic and tried to add the module "Lissajou" to the toolbox. It worked, appeared in the category where it should. Then I closed your schematic - and the module was gone. Disappeared immediatly from the category.
Now I'm sure it is the module and not your pc. Whatever is in there, it's something that Flowstone doesn't like.

EDIT: Also, the file is still referenced in the .tag file, the file exists in user - it just disappears from Flowstone's list view.

[tulamide]

Got it!

The issue can be found in the module clock. There's a prim I never heard of ("FL Studio" or something, I forgot the name). However, its function is to hide a module either in Synthmaker (yes, the prim is that old) or in FL Synthmaker. Delte it and it should work.

EDIT: That also explains why PHI had no issues!

[Spogg]

Yesssss!!!!


Now it works you eagle-eyed tulamide you!

What a funny Prim

Thanks for that my friend.

Cheers

Spogg

[BobF]

Hi gang,

So what is the exact name of this prim, so we can all check for it? I found one called clock!

Thanks.....

[Spogg]

here it is...

Cheers

Spogg

[tulamide]

Haha,

now I know the purpose of that tiny little button on the side of my glasses, labeled "eev". Had a look at my glasses' manual:

"Press eev once to enable eagle-eye-vision. In this mode the glasses focus on unusual encounters. A tracker sound will lead you near the source. Parts of this technology are licensed from Stark Industries."

[Spogg]

I need those glasses.

[Perfect Human Interface]

EDIT: That also explains why PHI had no issues!

Indeed, I never even considered this could be an issue. I wonder if I've ever shared anything with one of these in it.

My understanding is that this is meant for things that include modules specific to the FL version, so they don't show up (broken) in the other versions. My guess is that the non-FL install includes the same modules, necessitating this thingy. I don't see any good reason why and end user would want to add this module to their own schematics. Just my own thoughts.

[tulamide]

My understanding is that this is meant for things that include modules specific to the FL version, so they don't show up (broken) in the other versions.

That might have been true when Flowstone was still Synthmaker. But Flowstone as of today automatically hides elements that are not usable in the FL version and vice versa. Best example: You have an audio out prim, that I don't have. But I have an asio out prim that you don't have. Behind the scenes they both exist in both versions, but are taken from a schematic depending on which version you are using (or even exchanged in case of the audio out prim), and are hidden in the module list.
I don't see any application for this prim nowadays (apart from bothering us).

[Perfect Human Interface]

Well I think it's not to prevent errors or crashes per se, but rather so that people who use the non-FL version don't get stock items in their toolbox that don't work correctly. Again, I don't think there's any good reason for an end-user to add the prim to something, but there are a few (very few) stock modules that come with the FL version that include this, including that "clock" module (if I remember correctly one of the PPQ prims works slightly different in the FL version, I don't remember how).