Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cycle actions using toggle states from other cycle actions... #618

Closed
Jeff0S opened this issue Jul 8, 2014 · 4 comments
Closed

Cycle actions using toggle states from other cycle actions... #618

Jeff0S opened this issue Jul 8, 2014 · 4 comments

Comments

@Jeff0S
Copy link
Member

@Jeff0S Jeff0S commented Jul 8, 2014

From OuttrOMu...@gmail.com on January 15, 2014 22:34:37

Since cycle actions report toggle states, they should be able to use those states for conditional instructions (IF, ELSE etc).

Basically, I have a toolbar full of cycle actions (my fx compare toolbar), but need only ONE of them toggled on at a time (the last state loaded should be the only button lit up, for easy reference), so I tried to make them toggle off any others that are on.

Not sure why it doesn't work? I thought this had been discussed/resolved, but I can't find where I read about it...

Would help a lot, only thing I'm really missing for cycle actions, hopefully this is possible, as much more sophisticated cycle actions would be possible.

Thanks!

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=618

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on January 16, 2014 07:23:54

if that was not working, it would be a bug (not a FR, indeed) but I can't repro here, everything OK.
please can you export your cycle actions and attach them here? oh! and please tell me which of these cycle actions is not working as you expect?
also what are you REAPER/OS specs?
TIA!

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on January 24, 2014 00:57:08

Thanks for the details ;-)

Actually, I think I found the issue: your CA#2 is using a CA#1 and this CA#1 starts with an IF (or IF NOT) statement, right?

If so, this will be fixed soon (easy one, I think I can sneak it for the next release...).

Status: Started
Owner: jeffos...@gmail.com
Labels: OpSys-All

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on January 24, 2014 00:57:38

Labels: -Type-Enhancement Type-Defect

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on January 24, 2014 15:44:45

This issue was closed by revision r1186 .

Status: Fixed

@Jeff0S Jeff0S closed this Jul 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.