Home › Forums › General › Using Ctrlr › image toggle button
- This topic has 10 replies, 4 voices, and was last updated 12 years, 10 months ago by Layzer2.
-
AuthorPosts
-
June 10, 2011 at 9:52 pm #40
there seems to be a glitch in the image toggle button when setting the min-max values.
i need to send a sysex message like so …. F0 43 1A 1B 01 XX F7
F0 43 1A 1B 02 XX F7
F0 43 1A 1B 03 XX F7
F0 43 1A 1B 04 XX F7I put the first message in the initial send area and the other three in the multi list area.
i make an image button and give it the values 0 and 1 and set off value as 0 on value as 1
load a button image that is 20×40 that contains the on-off state images stacked on each other.
click the button, ok all is well… i see the 4 messages sent with the values 1 and 0 accordingly.
i need to make 7 more buttons… each new one, changing the min-max incrementally by 1
so next button in value box i put: 0 = 1
1 = 2and set the "off" state value to 1 "on" state to 2
click it… it turns on and off and i see 1 and 2 sent in the sysex monitor. so far so good.
problem happens on the 3rd button.
i set it up with values: 0 = 2
1 = 3set "off" state to 2, "on" state to 3
click…the button image stays off, but the values are sent correctly.
i see 2 and 3 sent in the sysex monitor. strange. why does the image
not toggle on and off?heres the weird part. use a regular toggle button and it all works fine!
so heres the deal, i’ll use the regular toggle button for now.
but i can see this being a problem for other people.just out of curiosity i made a button image that is 20×160 with 4 button state images in it….
same results. *scratches head*June 10, 2011 at 10:31 pm #1001You need to make sure the Frame attributes are the same size as your button graphic
June 11, 2011 at 1:12 am #1002Hi Filch,
button attributs were set correctly hight = 20, width = 20.
the button works fine up until i set on state value = 4, off state = 3…. the message walues are sent, but the image stays in off state.June 11, 2011 at 6:04 am #1003From what I understand, ctrlr does not currently support more than 2 images , so a 4 state button won’t work.
Just tested : Changing the value for uiImageButton On State = , and Button Off State = , to anything other than 1,0 , the image does not change as you describe. Interesting for me, if my on/off state is anything but 1,0 , it will not send out the correct value over midi. It sends 1 every time, on or off. Once I revert back to 1,0 it sends those values out correctly.
I’ve also tested this out on Mostrum’s WaveXT v1.99 panel , and the behavior is the same. Change the value to anything other than 0,1 , the image stops working and the values sent are not correct.
June 11, 2011 at 3:48 pm #1000yup….
seems to me that putting 3 and 4 in the buttons values box and setting the off state to 3, on state to 4 on the slider values
should toggle the button image on and off and the 3 and 4 values sent alternately with each click….but it doesnt happen. ” title=”Sad” />
i played around with the "button is toggle" turning that on and off, but the button disappears completely when parameter is
turned off.June 19, 2011 at 2:12 am #999I think it’s actually the multi-messages that are not working right at the moment. you can use a four frame imageButton to cycle through four controller change messages.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
June 24, 2011 at 5:52 am #997ironically, I double posted this next follow up….
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
June 24, 2011 at 5:54 am #996Ok so I can reproduce what layzer was mentioning – the multi state buttons are now not working as of 526. I’m finally noticing this now after having some time to work with ctrlr again. probably related to the fact that every button and the note-on, note-offs are all triggering duplicate messages.
I have one image button which has three image states, it should be sending 0, 1 and 2, but on one click it’s sending 0 (three times), then 1 (twice), and then cycles back to sending 0 three times on mouse up.
every button and even the keyboard is sending multiple messages on mouse up. . certainly screwing things up for a lot of people scratching their heads if they’re not looking at the midi monitor.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
June 25, 2011 at 12:36 am #995will look at that, i was focued on the LUA part of Ctrlr but it looks like there is some work to be done here.
June 25, 2011 at 2:14 am #998cool. I’m sure you probably wont miss it but I filed a more detailed bug report on the duplicate message bug.. seems its happening with every modulator if you watch the midi monitor.. most of the time it’s pretty unnoticableunless you’re looking for it.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
June 25, 2011 at 8:48 am #1004the modulators assigned as "multi sysex" also has issues. seems to forget it should be a multi sysex modulator when you close, and reopen the controller. i have a panel with a button that has 4 sysex strings in the multi window, but only sends F0 00 F7 from the single slot when i reload the controller. check it.
-
AuthorPosts
- The forum ‘Using Ctrlr’ is closed to new topics and replies.