Sannyasin Brahmanathaswami wrote:
> Ali, here's a proposal for one possible UX scenario for setting
> behaviors in a "WSIWIG" way...
Seems simpler to just have an object picker dialog, ideally with Miller
columns for simple navigation.
Ali, I have one I wrote for behavior selection a while ba
Ali, here's a proposal for one possible UX scenario for setting behaviors in a
"WSIWIG" way
Adobe solved this already in a similar use case for setting book marks in
Acrobat.
create book mark (button or control on card 1 in our LC way…)
If action is to go to another page, then a "hanging" pal
Indeed that was the decision, it's a somewhat tricky one. We're open to
suggestions of how to improve it! (Perhaps there should be a card submenu?)
Stacks can be behaviours now (particularly useful with script-only stacks),
hence the presence of stacks on that menu.
On Wed, 25 May 2016 at 20:36,
Paul… great! that works. tks
is that documented somewhere? Semi-unintuitive.. but I guess is also makes
sense… UX decision… build some horrible long cascading menu with all buttons on
all cards (as behavior options) or … leave the inspector of open and *then*
navigate to your behaviors card.
Try this:
Go to card 2
Open the Project Browser and expand the view for card 1
Right click on the target button of card 1 in the PB and choose ‘Property
Inspector’
The PI for the button on card 1 will now allow you to link the behaviour to the
button on cards 2
HTH
Paul
> On May 25, 2016, at
LC 8 GM
scenario:
create card "Selections" --> card 1
create card "behaviors" --> card 2
on card 1 create several buttons
on card 2 create one button which will server as the behavior for the buttons
on card one
go to card 1
select a button, click on the behaviors icon in its property inspe
