Re: How to select behavior on another card in LC8
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 back. If you don't I can update mine to allow selecting stacks and submit it. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: How to select behavior on another card in LC8
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" palette pops upand over lays the page… User now navigations through the document and when he finds the target, clicks "set link" So let's translate this for our use case: 1. User clicks the behavior button icon in the property inspector for Control-X 2. Instead of a menu a small palette stack opens. behind the scenes you issue a "Push Card" to the top stack top to bottom the palette looks like this: -- Traverse your stack(s) for more behaviors # you could even have a next and previous icons to dispatch go next card and go previous card to the top stack I have this on some of the plugins for my own stacks # display the possible parent controls as you do now in the menu: [list field "Available Behaviors"] Button "apples Button "oranges" etc. Stacks # this will remain sticky --Some Other Stack -- Some other stack -- Now as soon as the user traverses the top stack the palette contents of fld "Available Behaviors" updates to show the behaviors on that card… the inspector is still open and lock to the object in Card one. As soon as the user chooses a behavior: pop card (of top stack) If the users closes the inspector… then auto close the Available Behaviors palette and do not pop card. Assume the navigated to some other card and decide to exit this operation and want to do something where they are now. BR On 5/25/16, 10:44 AM, "use-livecode on behalf of Ali Lloyd" wrote: >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. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: How to select behavior on another card in LC8
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, Sannyasin Brahmanathaswami wrote: > 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. > > > On 5/25/16, 9:29 AM, "use-livecode on behalf of Paul Hibbert" < > use-livecode-boun...@lists.runrev.com on behalf of p...@livecode.org> > wrote: > > >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 > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: How to select behavior on another card in LC8
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. On 5/25/16, 9:29 AM, "use-livecode on behalf of Paul Hibbert" wrote: >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 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: How to select behavior on another card in LC8
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 12:15 PM, Sannyasin Brahmanathaswami > wrote: > > 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 inspector > > The only buttons that appear as choices are the ones on card 1 > > I thought (could be wrong) in an earlier version… there was a way to navigate > to buttons on other cards to choose them as behaviors, but I'm not seeing any > way to choose the button on card 2 as the behavior for the button on card one > currently being inspected… you can go down to "stack" but this doesn't expose > any other cards/controls…and actually does an odd thing. you can set the > behavior to a stack name. I think that's just wrong… right? > > what am I missing? At this point we have to use the old tedious way of > manually getting the long ID of the button on card 2 and then pasting this > into the behavior > > submitted already as a bug: http://quality.livecode.com/show_bug.cgi?id=17732 > > please add anything else relative to setting behaviors that needs fixed > > tks > > BR > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
How to select behavior on another card in LC8
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 inspector The only buttons that appear as choices are the ones on card 1 I thought (could be wrong) in an earlier version… there was a way to navigate to buttons on other cards to choose them as behaviors, but I'm not seeing any way to choose the button on card 2 as the behavior for the button on card one currently being inspected… you can go down to "stack" but this doesn't expose any other cards/controls…and actually does an odd thing. you can set the behavior to a stack name. I think that's just wrong… right? what am I missing? At this point we have to use the old tedious way of manually getting the long ID of the button on card 2 and then pasting this into the behavior submitted already as a bug: http://quality.livecode.com/show_bug.cgi?id=17732 please add anything else relative to setting behaviors that needs fixed tks BR ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
