Some help needed in creating CYCLE Pointer command. Care to lend a hand?

[toddmd2]

I like to think I'm pretty proficient with Pinnacle, but CYCLE Pointers still confuse me greatly. Here is what I am trying to accomplish, maybe you can help:

TOGGLE ON Command:
On Activation
Shift Mode Red

TOGGLE OFF Command:
On Deactivation
Shift Mode Unshifted

The above 2 commands would then get rolled into a cycle command.

Now, I want to add a CYCLE Pointer In my cycle command because there are numerous ways to toggle the TOGGLE ON command off without specifically using the TOGGLE OFF command. This is the proper situation in which to use a cycle pointer correct? How would I go about putting that command together?

Here's what it should do:

Press X button
TOGGLE ON
(Red shift mode)
press X button
TOGGLE OFF
(Unshifted shift mode)

-or this-

Press X button
TOGGLE ON
(Red shift mode)
A different button is pressed causing TOGGLE ON to be toggled off without actually firing the TOGGLE OFF command
(Unshifted shift mode)
Press X button
TOGGLE ON
(Red shift mode)

How would I set up the pointers to make that happen?

[Thalia]

Let me see if I get what you want: you are trying to toggle of the shift mode, without firing toggle off? Or are you trying to get back to un-shifted mode by pressing a button other than X? Because why not just use another toggle on that sends you back to un-shifted?

Either you are over complicating things, or I'm missing something. What is it game/application wise that you want? Maybe that will help clarify things?

I cant tell you how many times I've spend hours on an overcomplicated setup of press/hold, cycle commands and different configurations and shift modes, only to suddenly realize I could do the exact same thing if I just used sticky mode after a certain event. D-OH!

EDIT: Am I correct that the intended cycle only consists of redshift on/redshift off? Because in that case, if a dual command doesn't do it for you, then maybe instead of cycles and cycle pointers, you could make a loop back with a strategically placed separator step?

[toddmd2]

As I understand it you want to use a cycle pointer command if the command in question can be reset to its original state by any other action other than the one you intended (toggle off).

In this case I want to be able to open a map by pressing X (shifting it to a red state that adds different functionality), the map can also be closed by a number of different key presses other than X. In this case a cycle pointer is needed to reset the command to its original toggled off state in the event of the map being closed with any other key press than X. Am I correct that a cycle pointer is needed in this situation?

[Pinnacle [Rob]]

Yes, it does sound like a cycle pointer would help you...

If you have a command like you described...
Press X button
TOGGLE ON
(Red shift mode)
press X button
TOGGLE OFF
(Unshifted shift mode)


Well first I notice you say "press X button" on both sides of that command... so are you using a "sticky" behavior?
Also if your command is just to turn a shift-mode button on or off, there usually should be a reason to use a command, otherwise you can just use a shift-mode button directly with a "behavior adjustment" (but since you mention a cycle command, perhaps that has to do with it, see more about my questions regarding your cycle command below)

Normally a command is like this, and I will use a simple key to demonstrate...

Activated Event
key SPACEBAR down
Deactivated Event
key SPACEBAR up

So if you assigned a command like that to your X Button (on Xbox360 controller, I assume) then it will send the spacebar down when you press X and release spacebar when you let go of the X Button.

Thus, I'm not sure what your goal is in terms of the shift-mode button... do you want to HOLD TO SHIFT or do you want to TOGGLE SHIFT with your X Button? Both are possible, and pretty simple to setup, but if you are trying to combine advanced functionality with that... then it's important that I understand what you are trying to do with the straight shift-mode button (before you may combine it with other advanced functionality).

Also, what does a Cycle Command have to do with your goal here? I'm still not sure I understand, and I think that Thalia may have been correct that you simple need a "sticky" behavior to handle all this for you. In the example command that I gave above, for a SPACEBAR key to be sent when the X Button is down and SPACEBAR to stop being sent when you release the X Button... well adding a "sticky" behavior to a button that has that command will cause the "Activated Event" (key SPACEBAR down) to be fired when you press X Button but NOT to send the "Deactivated Event" (key SPACEBAR up) until you press the X Button again. As described above, normally the "Deactivated Event" fires when you release the X Button... but with the "sticky" behavior attached, it will only fire 1 event at a time (on press) as opposed to firing 2 events (on press/on release).

I hope that might clarify some of the functionality for you, but if you have more questions then I need some answers to the questions I asked above for clarification on your intended goals.