slowed response time in the core module

Bernd Scheurer

i built a small core circuit that allows me a realistic displayed button, depending on a higher-level main switch. if the main switch is off, the button (released/pressed) is without lighting. if the main switch is pressed, the button (released/pressed) is illuminated.

this works fine so far. only the button “hangs” sometimes. it feels like he doesn't notice every mouse click. i suspect i've missed something fundamental (again), but i can't figure out what it is. has anyone a idea?

.ens-file ist attached.

thank you in advance for all the tips.

regards, bernd

CoreButton.ens.zip

colB

Yep, a merge fixes this problem

However, mouse area is maybe not the best approach here!

Problem is that you don't have midi learn with a mouse area, so it's kinda non-standard.

An alternative method is to use a regular button, but make it's image completely transparent, and put your multi Picture behind it. That way, you get the same functionality and look, but it's a regular GUI button, so you get midi, so it's more intuitive.

colB

I'm away from my pc so can't check your ens...

I'm wondering if you used a mouse area?

If so, you need to merge the MB and dbl (double click) output. Otherwise if you click too fast, it will register as double click and be ignored.

Bernd Scheurer

you guessed correctly, i use a mouse area. thank you very much for the tip, i'll try that out later because i have guests coming soon. thank you!

colB

Yep, a merge fixes this problem

However, mouse area is maybe not the best approach here!

Problem is that you don't have midi learn with a mouse area, so it's kinda non-standard.

An alternative method is to use a regular button, but make it's image completely transparent, and put your multi Picture behind it. That way, you get the same functionality and look, but it's a regular GUI button, so you get midi, so it's more intuitive.

Bernd Scheurer

i thought about that too. however, the button is difficult to find in the layout if it is completely transparent. but i'll take that with me as an idea. in the current case it involves 21 buttons, which can hardly be controlled from the outside via MIDI. the solution with the merge module definitely works great for the moment. thank you for that hint.