Your comments
fa 10 anys
Just updating this thread to note that this problem has been fixed. Renaming a project group changes the name of the folder, and the project group contains the same apps as it did before it was renamed.
Hi Ranco, I wanted to check in with you about this glitch. Have you encountered this more in the recent versions of InteractBuilder?
Thank you so much for the update! That really helps when we can separate what is completed.
Hi Truman,
We're going to look into making this option available. For now, the action sets do show up separately as soon as they are indented under another action set.
If you have an instance where the parent action set has the same interaction as the child action sets, then you can temporarily give that one a different interaction (in the element's Action tab), chain the action sets, and then set the parent action set's interaction back to what it should be.
For example, if I have a (none)-Animate action set that is meant to play on page load and be followed by a different (none)-Animate action set, then I can set the interaction of the first action set to OnBrowserClose (or any interaction), chain the action sets, and then change the interaction back to "none," (If you need the parent action set to start on page load and there is no browser on the page, you could even leave the interaction as "OnBrowserClose.")
If there are other behaviors involved on the same element, then another way of separating your action set group would be to chain them after any of the other action sets so that they separate, then chaining them in the correct sequence before bringing the parent action set back to the left edge of the action set table.
We're going to look into making this option available. For now, the action sets do show up separately as soon as they are indented under another action set.
If you have an instance where the parent action set has the same interaction as the child action sets, then you can temporarily give that one a different interaction (in the element's Action tab), chain the action sets, and then set the parent action set's interaction back to what it should be.
For example, if I have a (none)-Animate action set that is meant to play on page load and be followed by a different (none)-Animate action set, then I can set the interaction of the first action set to OnBrowserClose (or any interaction), chain the action sets, and then change the interaction back to "none," (If you need the parent action set to start on page load and there is no browser on the page, you could even leave the interaction as "OnBrowserClose.")
If there are other behaviors involved on the same element, then another way of separating your action set group would be to chain them after any of the other action sets so that they separate, then chaining them in the correct sequence before bringing the parent action set back to the left edge of the action set table.
Customer support service by UserEcho