pages.setActiveControlSet(controlSetId)

General discussion
1

I wonder if the subjected function still works or what I am doing wrong.

I used to use the following function:

image
image369×113 12.8 KB

… a lot i.e. for pads located in control set 2 or 3 before firmware 4.n and it always worked.

Today I even created a blanc project with only one control to confirm it and it doesn’t work there also.

On the E1’s screen sometimes a short “flashing” jump to control set 1 is visible but then it returns back to control set 3 within milliseconds.

Any ideas? Thanks in advance.

2

@HaPe would you send me a link to your test preset? You do not need to make it public - just send a link.

I created a preset with one pad and assigned the function you posted to it. It works as I would expect. Active control set is switched to 1 even if the pad is in control set 3. Of course, sometimes, you can see that it jumps to 3 and then back to 1. when the "Touch switches control sets” option is enabled in the settings.

I tested it on 4.1.1 and 3.6.1 - I am getting the same behaviour.

1 Like
3

Hi Martin,

Thanks a lot for getting back to me.

After all these testing yesterday I was a bit distracted so my description wasn’t quite right. In addition the preset with just one pad assigned directly to this function which didn’t work yesterday worked today after a new start of the E1.

But I was used to use “pages.setActiveControlSet(1)“ kind of “embedded” in other functions and even with pad controls set to “toggle”: And this still doesn’t work. The test preset contains three pad controls. The first one is directly assigned to the function “setControlset1” and works. The second one is also assigned to it but works as a toggle and doesn’t work. Number 3 has a different function assigned but the command “ pages.setActiveControlSet(1) “ integrated and also doesn’t work. It is visible that the control set 1 is activated just very short and then it jumps back to 3.

And I am sure that all these things used to work fine month ago before v. 4 because I worked with this preset a lot and never had any issues like now.

Thanks again.

1 Like
4

@hape and I resolved the issue over the DM. The “Touch switches the control sets” option in the User Interface settings did the trick.

1 Like
5

Thanks again so much for your help. Unfortunately I stumbled upon something new I’m gonna open another topic for. :man_shrugging:t3:

Update: Apparently, a self-healing process has taken place… :sweat_smile: It now works again, at least at the moment…