Re: Bad Crash on Attempt to Group Radio Buttons

Bob Sneidar wrote: >> On Aug 28, 2017, at 12:01 , Randy Hengst wrote: >> >> Wow, if I set the cantSelect of my background graphic to true AND set >> the grc to disabled… > > grc is not a token. But is is, first introduced to the xTalk world by Bill Appleton in SuperCard 1.0, following the

Re: Bad Crash on Attempt to Group Radio Buttons

so then disable the grc, not set the grc to disabled. Got it. Bob S > On Aug 28, 2017, at 16:20 , Brian Milby via use-livecode > wrote: > > grc is a synonym for graphic actually ___ use-livecode mailing list

Re: Bad Crash on Attempt to Group Radio Buttons

ok I read back on the posts and that does in fact work. At that point you can set the geometry of any object so that no matter what you do with the size of the window they will adjust to compensate. I LIKE IT!!! Bob S > On Aug 28, 2017, at 16:15 , Bob Sneidar via use-livecode >

Re: Bad Crash on Attempt to Group Radio Buttons

grc is a synonym for graphic actually On Mon, Aug 28, 2017 at 6:15 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > grc is not a token. I guess you are using an acronym. I hate acronyms. ;-) > > Bob S > > > > On Aug 28, 2017, at 12:01 , Randy Hengst via use-livecode < >

Re: Bad Crash on Attempt to Group Radio Buttons

grc is not a token. I guess you are using an acronym. I hate acronyms. ;-) Bob S > On Aug 28, 2017, at 12:01 , Randy Hengst via use-livecode > wrote: > > Wow, if I set the cantSelect of my background graphic to true AND set the grc > to disabled… I can do

Re: Bad Crash on Attempt to Group Radio Buttons

RichardG wrote: > >> I have used cantSelect before to stop selection of a background image >> that has lots of objects on top. It means you can drag select them and >> won?t accidentally click-drag and move your background. > > How? Disable it in addition to setting the cantselect. Jim

Re: Bad Crash on Attempt to Group Radio Buttons

Wow, if I set the cantSelect of my background graphic to true AND set the grc to disabled… I can do exactly what I was talking about… nice. Both have to be set… just using one or the other doesn’t work. Thanks Paul. > On Aug 28, 2017, at 12:23 PM, Paul Hibbert via use-livecode >

Re: Bad Crash on Attempt to Group Radio Buttons

Paul Hibbert wrote: > On Aug 28, 2017, at 7:07 AM, Randy Hengst wrote: >> >> I would find it very handy if when the cantSelect is true, you could >> still drag to select objects that are above the control with >> cantSelect true… >> >> In other words, the ability to select the other controls

Re: Bad Crash on Attempt to Group Radio Buttons

Ah! Yeah that makes my particular application unusable. I was hoping to have different sections of a card with different background images, and be able to drag-select everythign but the background images. Currently I have the background pattern of a card set to a hidden image, then I have other

Re: Bad Crash on Attempt to Group Radio Buttons

On Aug 28, 2017, at 7:07 AM, Randy Hengst via use-livecode wrote: > > I would find it very handy if when the cantSelect is true, you could still > drag to select objects that are above the control with cantSelect true… > > In other words, the ability to select

Re: Bad Crash on Attempt to Group Radio Buttons

Monte Goulding wrote: > I have used cantSelect before to stop selection of a background image > that has lots of objects on top. It means you can drag select them and > won’t accidentally click-drag and move your background. How? As designed, what we call "cantSelect" works like

Re: Bad Crash on Attempt to Group Radio Buttons

Well, cantSelect is a step toward a solution for making multi-mode regions within a window, as I noted just above the section of my post you quoted: Scott Raney added the cantSelect property after a long discussion I had with him about building custom drawing environments. I had

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/28/2017 07:53 AM, Richard Gaskin via use-livecode wrote: But since the property that more accurately behaves as AlwaysBrowseMode is currently called "cantSelection", what might we name a property that was limited to non-selection without invoking a tool mode different than the current

Re: Bad Crash on Attempt to Group Radio Buttons

That would be useful to me now that I think about it. Bob S > On Aug 27, 2017, at 13:36 , Monte Goulding via use-livecode > wrote: > > I have used cantSelect before to stop selection of a background image that > has lots of objects on top. It means you can

Re: Bad Crash on Attempt to Group Radio Buttons

Randy Hengst wrote: > I would find it very handy if when the cantSelect is true, you could > still drag to select objects that are above the control with > cantSelect true… > > In other words, the ability to select the other controls with click > and drag when the initial click is within the

Re: Bad Crash on Attempt to Group Radio Buttons

I would find it very handy if when the cantSelect is true, you could still drag to select objects that are above the control with cantSelect true… In other words, the ability to select the other controls with click and drag when the initial click is within the rect of the control (usually a

Re: Bad Crash on Attempt to Group Radio Buttons

Richard: Hmmm, this could be really useful a whole responsive palette of control on the side of a card, (instead of a separate palette stack) while continuing to dev in the main region. useful for dev. In fact doesn't this solve a core UX, that is not "ancient"by any means?: A drawing

Re: Bad Crash on Attempt to Group Radio Buttons

this is a really useful prop… too bad it is not exposed in the PI "use case for it" OH Boy! us page lay people lock background objects all the time… once a subset of elements are "locked down" design wise.. you don't what them moving about. I'll be using this a lot now that I found it… But

Re: Bad Crash on Attempt to Group Radio Buttons

PR submitted... https://github.com/livecode/livecode-ide/pull/1713 http://quality.livecode.com/show_bug.cgi?id=20289 On Sun, Aug 27, 2017 at 4:33 PM, Brian Milby wrote: > I think that may be better. > > Since JavaScript doesn't preserve pre-sort order, I think additional >

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/27/2017 06:21 PM, Richard Gaskin via use-livecode wrote: The pointer tool, like any of the tools, is just an interaction mode. Any capabilities beyond manipulating layout are defined by your scripts. OK - so we're talking about outside the IDE. So the cantSelect property comes into

Re: Bad Crash on Attempt to Group Radio Buttons

Mark Wieder wrote: > On 08/27/2017 04:49 PM, Richard Gaskin via use-livecode wrote: >> Drawing != development. > > Maybe I'm only partially understanding this then. My take on this is > that the cantSelect property really only comes into play when the > edit tool (or whatever it's called these

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/27/2017 04:49 PM, Richard Gaskin via use-livecode wrote: Mark Wieder wrote: On 08/27/2017 01:42 PM, Marty Knapp via use-livecode wrote: I use this feature extensively in an app where there is card that has objects that users can select to change properties (line width, color, font, etc)

Re: Bad Crash on Attempt to Group Radio Buttons

Mark Wieder wrote: On 08/27/2017 01:42 PM, Marty Knapp via use-livecode wrote: I use this feature extensively in an app where there is card that has objects that users can select to change properties (line width, color, font, etc) and at the top of the window is a toolbar with font menu, etc. I

Re: Bad Crash on Attempt to Group Radio Buttons

I sent this reply once already, several hours ago. It hasn't arrived, so I thought I'd try again. If you get two copies, I apologize on behalf of the listserver: On 8/27/17 1:09 PM, Sannyasin Brahmanathaswami via use-livecode wrote: > JQ wrote > CantSelect disallows selection by the

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/27/2017 01:36 PM, Monte Goulding via use-livecode wrote: I have used cantSelect before to stop selection of a background image that has lots of objects on top. It means you can drag select them and won’t accidentally click-drag and move your background. It’s better than lockLocation

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/27/2017 01:42 PM, Marty Knapp via use-livecode wrote: I use this feature extensively in an app where there is card that has objects that users can select to change properties (line width, color, font, etc) and at the top of the window is a toolbar with font menu, etc. I don't want the

Re: Bad Crash on Attempt to Group Radio Buttons

In development it can be handy if you have an object that shouldn't move or change, but you want to drag a selection around surrounding objects to select them. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: Bad Crash on Attempt to Group Radio Buttons

I think that may be better. Since JavaScript doesn't preserve pre-sort order, I think additional comparisons are needed to maintain the alpha sort. While we can use a trailing "\b" to match word ending (makes exact word be prioritized), using something like a quote

Re: Bad Crash on Attempt to Group Radio Buttons

> On 28 Aug 2017, at 4:08 am, J. Landman Gay via use-livecode > wrote: > >> I've been working on the dictionary and would like to improve it even more. > > Your name will be praised. :) Brian’s name is praised already! He’s certainly pitching in! As far as the

Re: Bad Crash on Attempt to Group Radio Buttons

I use this feature extensively in an app where there is card that has objects that users can select to change properties (line width, color, font, etc) and at the top of the window is a toolbar with font menu, etc. I don't want the user to be able to select the toolbar controls and

Re: Bad Crash on Attempt to Group Radio Buttons

> On 28 Aug 2017, at 6:29 am, Mark Wieder via use-livecode > wrote: > >> CantSelect is false by default, and since it isn't in the project browser, >> new users are unlikely to know about it. They're also unlikely to dig into >> the Plugins menu to show the app

Re: Bad Crash on Attempt to Group Radio Buttons

> On 28 Aug 2017, at 4:09 am, Sannyasin Brahmanathaswami via use-livecode > wrote: > >CantSelect disallows selection by the edit tool, mostly used in >development, but doesn't change the message path. > > Hmm.. doesn't this comprise a Noobie Gotcha? >

Re: Bad Crash on Attempt to Group Radio Buttons

On 08/27/2017 01:10 PM, J. Landman Gay via use-livecode wrote: CantSelect is false by default, and since it isn't in the project browser, new users are unlikely to know about it. They're also unlikely to dig into the Plugins menu to show the app browser, so mistakes would probably be rare.

Re: Bad Crash on Attempt to Group Radio Buttons

On 8/27/17 1:09 PM, Sannyasin Brahmanathaswami via use-livecode wrote: JQ wrote CantSelect disallows selection by the edit tool, mostly used in development, but doesn't change the message path. Hmm.. doesn't this comprise a Noobie Gotcha? cantSelect is not exposed in the PI for any

Re: Bad Crash on Attempt to Group Radio Buttons

JQ wrote CantSelect disallows selection by the edit tool, mostly used in development, but doesn't change the message path. Hmm.. doesn't this comprise a Noobie Gotcha? cantSelect is not exposed in the PI for any object. if it was, then toggling this in the ABrowser would trigger the

Re: Bad Crash on Attempt to Group Radio Buttons

On 8/27/17 12:48 PM, Brian Milby via use-livecode wrote: I've been working on the dictionary and would like to improve it even more. Your name will be praised. :) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: Bad Crash on Attempt to Group Radio Buttons

I've been working on the dictionary and would like to improve it even more. Changes to the selection logic will probably need concurrence from the LC folks.Right now the search is performed on the name and the syntax. Priority is given to terms that match the start of a word.

Re: Bad Crash on Attempt to Group Radio Buttons

Ah - thanks Sent from my iPhone > On Aug 27, 2017, at 11:39 AM, J. Landman Gay via use-livecode > wrote: > > CantSelect disallows selection by the edit tool, mostly used in development, > but doesn't change the message path. > > -- > Jacqueline Landman Gay

Re: Bad Crash on Attempt to Group Radio Buttons

CantSelect disallows selection by the edit tool, mostly used in development, but doesn't change the message path. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On August 27, 2017 9:25:28 AM Jonathan Lynch

Re: Bad Crash on Attempt to Group Radio Buttons

If you click a button with cantselect set to true, what object receives the click? Sent from my iPhone On Aug 27, 2017, at 6:20 AM, hh via use-livecode wrote: >> JLG wrote: >> ... But it should be easier. > > You could use tinyDictionary. > >

Re: Bad Crash on Attempt to Group Radio Buttons

Yes, Tiny Dictionary is brilliant. But does it integrate with the script editor yet? Will new users know they should download a third party solution to get a fully functional dictionary? I can usually find what I need because I know most of the terminology but others won't. . -- Jacqueline

Re: Bad Crash on Attempt to Group Radio Buttons

> JLG wrote: > ... But it should be easier. You could use tinyDictionary. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: Bad Crash on Attempt to Group Radio Buttons

Thanks. But it should be easier. On 8/26/17 11:53 PM, Brian Milby via use-livecode wrote: "select\b" will make finding it a little easier. On Aug 26, 2017 at 11:49 PM, mailto:use-livecode@lists.runrev.com)> wrote: On 8/26/17 10:41 PM, Sannyasin Brahmanathaswami

Re: Bad Crash on Attempt to Group Radio Buttons

"select\b" will make finding it a little easier. > > On Aug 26, 2017 at 11:49 PM, (mailto:use-livecode@lists.runrev.com)> wrote: > > > > On 8/26/17 10:41 PM, Sannyasin Brahmanathaswami via use-livecode wrote: > > So, what is this "selectable" property? It's the

Re: Bad Crash on Attempt to Group Radio Buttons

On 8/26/17 10:41 PM, Sannyasin Brahmanathaswami via use-livecode wrote: So, what is this "selectable" property? It's the cantSelect property, which doesn't show up in any search I did in the dictionary. But if you search for "select" and scroll forever, it's in the list. It's also the first

Re: Bad Crash on Attempt to Group Radio Buttons

OK so editing groups was crashing LC on my Mac again today. I had pasted a grc into a group, could not select it, then closed the stack and LC crashed (reported here bug 20299) But when I reopened the stack the grc was there on the top layer of the group that I had edited before crashing. so

Re: Bad Crash on Attempt to Group Radio Buttons

> On 23 Aug 2017, at 1:47 pm, Sannyasin Brahmanathaswami via use-livecode > wrote: > > Before I report… anyone seeing this or know this has been addressed in more > recent versions. A crash log should help us find this relatively quickly if you can’t come up

Re: Bad Crash on Attempt to Group Radio Buttons

All crashes are bugs and need reporting. It sounds like in this case you had individual objects selected and tried to edit those as you would a group. The engine couldn't handle it. I've not had a crash if a group itself is selected when I choose "edit group". To create a group inside another

Bad Crash on Attempt to Group Radio Buttons

I had just now a really bad crash in 8.1.6 created custom control/group then I needed to create two groups of five @ radio buttons in that group. I layed out the radio buttons and then with selectedGroupedControls selected, I tried to group one set of radio buttons by selecting them and click