Re: Relayering Madness
On Thu, Mar 14, 2019 at 3:09 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Thanks Jacque, I did that of course, same result. I forgot that there is a > way of doing this using Navigator, by starting a drag on the group in > Navigator, THEN pressing the option key, and dropping it where you want it. > If you start with the option key it clones it instead. DOH! > I don't know what version of Navigator you have, but you shouldn't have to use the option key except when you want to clone something. If you're using the latest version and pressing the option key after you start dragging *doesn't* clone, let me know what you're doing; that's a bug. I just tried it and I can't replicate it. gc ___ 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: Relayering Madness
On Thu, Mar 14, 2019 at 4:24 PM J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I guess I'm not sure what the problem was, I relayer groups all the > time. I change the layer number in the group's property inspector > though, since I don't use the Project Browser. Maybe it's different there. > The Project Browser allows you to drag anything to any layer, in a group or out, and will make it happen. I believe (although I have not looked at the code lately) that it does this by setting relayerGroupedControls to true. Evidence for this is the fact that dragging a control to the layer just above a group -- just below the group in the Project Browser -- will place the control into the group. This is how Navigator used to work as well. Several updates ago I changed Navigator to use a sequence of steps involving editing groups, and setting relayerGroupedControls to true only if necessary, so that: 1. Dragging to the layer just above a group does *not* place the control into the group; just to the appropriate layer. 2. Dragging to a layer *in* a group moves the control into the group, at that layer. 3. The above works even with nested groups (just checked, and I'm very happy with my past self!) Meaning that if you have this: stack "Untitled 1" card id 1002 | group id 1011 (1011) | | group id 1006 (1006) | | | button "Button" (1003) | | | button "Button" (1007) | | | button "Button" (1004) | | | button "Button" (1005) | | | button "Button" (1009) | | button "Button" (1010) | | button "Button" (1008) | button "Button" (1012) | button "Button" (1013) And you drag button id 1013 just under button id 1009, you get this: stack "Untitled 1" card id 1002 | group id 1011 (1011) | | group id 1006 (1006) | | | button "Button" (1003) | | | button "Button" (1007) | | | button "Button" (1004) | | | button "Button" (1005) | | | button "Button" (1009) | | button "Button" (1013) | | button "Button" (1010) | | button "Button" (1008) | button "Button" (1012) Note that button id 1013 is now in group id 1011, but it is *not* in group id 1006. Holding the option/alt key is not needed for any of this. ___ 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: Relayering Madness
I guess I'm not sure what the problem was, I relayer groups all the time. I change the layer number in the group's property inspector though, since I don't use the Project Browser. Maybe it's different there. On 3/14/19 5:09 PM, Bob Sneidar via use-livecode wrote: Thanks Jacque, I did that of course, same result. I forgot that there is a way of doing this using Navigator, by starting a drag on the group in Navigator, THEN pressing the option key, and dropping it where you want it. If you start with the option key it clones it instead. DOH! If you purchase Navigator for nothing else, purchase it for this! Very nifty. Bob S On Mar 14, 2019, at 11:12 , J. Landman Gay via use-livecode wrote: The default is as you'd expect, relayerGroupedControls is false. The dictionary doesn't say it, but I believe the property is persistent until you turn it off or restart LC. So set it to false and try again. -- Jacqueline Landman Gay ___ 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 -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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: Relayering Madness
Thanks Jacque, I did that of course, same result. I forgot that there is a way of doing this using Navigator, by starting a drag on the group in Navigator, THEN pressing the option key, and dropping it where you want it. If you start with the option key it clones it instead. DOH! If you purchase Navigator for nothing else, purchase it for this! Very nifty. Bob S > On Mar 14, 2019, at 11:12 , J. Landman Gay via use-livecode > wrote: > > The default is as you'd expect, relayerGroupedControls is false. The > dictionary doesn't say it, but I believe the property is persistent until you > turn it off or restart LC. So set it to false and try again. > > -- > Jacqueline Landman Gay ___ 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: Relayering Madness
The default is as you'd expect, relayerGroupedControls is false. The dictionary doesn't say it, but I believe the property is persistent until you turn it off or restart LC. So set it to false and try again. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 14, 2019 10:35:32 AM Bob Sneidar via use-livecode wrote: Thanks Richard. So that is not the property I need. I still cannot relayer groups though, without moving a group inside another group. How do I make that stop? (And who the heck at RunRev thought that the default behavior when moving groups around should be to move one group INTO another group???) Bob S On Mar 14, 2019, at 08:13 , Richard Gaskin via use-livecode wrote: > Can someone tell me again what to do to prevent relayering from jacing > up my discreet groups?? If you conceptualize it as "relayerGroupControls" (emphasis on groups) I can understand the confusion. The actual property name is "relayerGroupedControls" (emphasis on things inside of groups), which should help align expectations with what it does. -- Richard Gaskin ___ 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: Relayering Madness
Thanks Richard. So that is not the property I need. I still cannot relayer groups though, without moving a group inside another group. How do I make that stop? (And who the heck at RunRev thought that the default behavior when moving groups around should be to move one group INTO another group???) Bob S > On Mar 14, 2019, at 08:13 , Richard Gaskin via use-livecode > wrote: > > > Can someone tell me again what to do to prevent relayering from jacing > > up my discreet groups?? > > If you conceptualize it as "relayerGroupControls" (emphasis on groups) I can > understand the confusion. > > The actual property name is "relayerGroupedControls" (emphasis on things > inside of groups), which should help align expectations with what it does. > > -- > Richard Gaskin ___ 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: Relayering Madness
Bob Sneidar wrote: > I am really at a loss when it comes to relayering groups. I read the > dictionary on relayerGroupControls and it appears to me while reading > it that if you set it to false, you can relayer groups by bringing > forward or sending backward and it won't become a part of another > group. In fact, the opposite is happening, and when I fix it one of > the two groups that got merged ends up all the way in front. > > Can someone tell me again what to do to prevent relayering from jacing > up my discreet groups?? If you conceptualize it as "relayerGroupControls" (emphasis on groups) I can understand the confusion. The actual property name is "relayerGroupedControls" (emphasis on things inside of groups), which should help align expectations with what it does. -- 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
Relayering Madness
I am really at a loss when it comes to relayering groups. I read the dictionary on relayerGroupControls and it appears to me while reading it that if you set it to false, you can relayer groups by bringing forward or sending backward and it won't become a part of another group. In fact, the opposite is happening, and when I fix it one of the two groups that got merged ends up all the way in front. Can someone tell me again what to do to prevent relayering from jacing up my discreet groups?? Bob S ___ 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