21
Replies
Hi,
You can definitively build your framework so this kind of "complex" widgets would be only designed once 
var w = new Window('dialog');
var btn = function(p, f) {
var btnGp = p.add('group');
btnGp.orientation='stack';
var blueButton = btnGp.add('button', undefined, 'BLUE');
var greenButton = btnGp.add('button', undefined, 'GREEN');
greenButton.visible = false;
var switchButtons = function() {
blueButton.visible = blueButton.visible? false : true;
greenButton.visible = greenButton.visible? false : true;
greenButton.visible && f && (f instanceof Function) && f();
}
blueButton.onClick = greenButton.onClick = switchButtons;
}
var f1 = function(){alert("f1")};
var f2 = function(){alert("f2")};
btn(w, f1 );
btn(w, f2 );
w.show();
I will add the below to my library 
I think it's a pretty easy work around to the problem.
function addBiState (_parent, UIType, state1Details, state2Details, groupDetails) {
var bounds, _string, setupProperties, newGroup;
if (groupDetails) {
bounds = groupDetails[0] && groupDetails[0];
_string = groupDetails[1] && groupDetails[1];
setupProperties = groupDetails[2] && groupDetails[2];
}
newGroup = _parent.add('group', bounds, _string, setupProperties);
newGroup.margins = [0,0,0,0];
newGroup.orientation='stack';
if (state1Details) {
bounds = state1Details[0] && state1Details[0];
_string = state1Details[1] && state1Details[1];
setupProperties = state1Details[2] && state1Details[2];
}
newGroup[0] = newGroup.add(UIType, bounds, _string, setupProperties);
if (state2Details) {
bounds = state2Details[0] && state2Details[0];
_string = state2Details[1] && state2Details[1];
setupProperties = state2Details[2] && state2Details[2];
}
newGroup[1] = newGroup.add(UIType, bounds, _string, setupProperties);
newGroup[1].visible = false;
return newGroup;
}
Group.prototype.biStateChange = function (state) {
if (state) {
this[+state].visible = true;
this[+!state].visible = false;
}
else {
this[0].visible = !this[0].visible;
this[1].visible = !this[1].visible;
}
}
/********** Example Usage *************/
var w = new Window('dialog'),
greenPen = w.graphics.newPen(w.graphics.PenType.SOLID_COLOR,[0, .6, .2],1),
yellowBrush =w.graphics.newBrush(w.graphics.BrushType.SOLID_COLOR,[1, 1, 0],1),
myBiStateButton = addBiState (w, 'button', [undefined, "Theme"], [undefined, "Green"]),
myBiStateStaticText = addBiState (w, 'staticText', [undefined, "Theme"], [undefined, "Green"]),
stGroup = w.add('group'),
st = stGroup.add('statictext', undefined, "Toggle"),
highlightGroup = addBiState(stGroup, 'group');
st = highlightGroup[0].add('statictext', undefined, "highlight")
st = highlightGroup[1].add('statictext', undefined, "highlight")
myBiStateButton[1].graphics.foregroundColor = greenPen;
myBiStateStaticText[1].graphics.foregroundColor = greenPen;
highlightGroup[1].graphics.backgroundColor = yellowBrush;
highlightGroup[0].margins = highlightGroup[1].margins = [3, 3, 3, 3];
stGroup.spacing = 4;
myBiStateButton.addEventListener ('mousedown', function () {
myBiStateButton.biStateChange();
myBiStateStaticText.biStateChange();
highlightGroup.biStateChange();
});
w.show();
Hi Trevor,
Thanks a lot for the credits
Aren't they issues with addEventListener with CC ? From now on I use a pseudo event class of my own that can dispatch "events" for UI & non UI items. That something I would use for sure here
Event-Driven Programming with ExtendScriptOzalto
Then "button" can fire an event independantly of ScriptUI bugs cycles
EventManager.dispatchEvent ("BUTTON_PRESSED");
FWIW,
Loic
Hi Loic,
Credit well deserved. This issue has be brought up numerous times and has quite some importance. The basic idea of indicating to the user that he's doing something wrong on the UI. The idea of the solution was your, I just put together a handy implementation of it. My idea was to get the 100 possible sets of foreground and background theme colors that exist and set the rgb's accordingly, yours has the big advantages of simplicity, and not being dependent on application or version.
Thanks for the interesting link I shall look at the code in detail when I get a chance. I could not comment on it without a good look.
The are issues with the events, Marc has a good pdf on it on his site that addresses some.
However I do use them very frequently and hope that I know how to navigate them safely.
I try steer clear of the standard SUI widgets and use ones from my private library.
Here's a screen shot of a batch Microsoft Word To InDesign script that I was working on recently (hope to release it some time in the next few months).
Note the checkbox and the radio buttons.
The radio buttons in particular are so much easier to work with than the standard SUI ones not having any limitations of the order or grouping where they are placed or which event triggers there action.
Regards,
Trevor
Hi Trevor,
Great work. Wish you the best with this product
Loic
AdChoices