BrainModular

Hi,
I'd like to store text fields content with a PM. How can I do that ?
Or perhaps there's a workaround I don't know... I have a collection of labels in front of a collection of seq switches, and I'd like to store the text with the PM :



I can enter the text in the patch window if it's much simpler.
Thanks for your help !

is the saved in preset option is activated in the text field module..?

It wasn't :rolleyes:
But the trouble remains. Now the texts are kind of mixed together, or a "i" appears for an empty field... strange.

Did you find a fix or workaround for this problem, la tenaille?

I'm trying to save some text fields within a preset for a patch I'm currently building and am having the same problem with their outputs getting corrupted.

I haven't found a fix. My workaround is a poly sub patch with 16 layers, each one containing 16 text fields. I switch the fields visible according to the PM number. Here is my subpatch :



My constant numbers are 0 (invisible) for the bottom module and 7 (popup window) for the top one.
Not simple, but I can edit the visible texts and store them with the PM.
Hope it helps

Yeah, that's a bit too much of a work-around for my laziness.

Given that I find text editing within Usine a bit clunky, my own work-around is a small piece of FastScript that can load a text file and extract a requested line - indexed from 0 - from it. It's behaviour when attempting to select invalid lines (beyond the file's end, for example) is selectable.

line-from-file.fastscript

I've got more highly featured text parsers for the larger systems I'm prototyping, but attaching this to the num outlet of a preset manager works well when all that's needed is varying text per preset (or whatever, e.g. it is also useful driven by the row/column selector of a matrix).

right, actually the text field is not stored in the preset but will be in the next release, if, of course, the saved in preset setting is activated.

@ynohtna : Waiting for this new release, the script is a good option!

well, the PM256 subpatch with its attendant list can also work that way. Here is the most current version I'm using (I think there were still bugs in the last one I posted)

http://www.sensomusic.com/forums/upload ... =pm512.pat


I will still welcome the new text field behaviour, though!

senso wrote:right, actually the text field is not stored in the preset but will be in the next release

Hi Senso,
It doesn't seem to work with the #9 update ?