Another bingo! The cantSelect does do it.
However, that seems to have to be set by a script. I understand that you then
can’t select it with the pointer tool to show the Property Inspector for it, so
not having a checkbox to set that property makes some sense. But it would be
nice to have that
> On 9 Oct 2016, at 5:33 PM, Peter Bogdanoff wrote:
>
> Card objects are still “unprotected”?
yes, although have you thought about setting the cantModify of the stack or the
cantSelect of the objects?
___
use-livecode mailing list
use-livecode@lists.
Yes, I didn’t know about selectGroupedControls.
Thank you! That definitely does the trick for groups.
Card objects are still “unprotected”?
On Oct 8, 2016, at 11:25 PM, Monte Goulding wrote:
>
>> On 9 Oct 2016, at 5:23 PM, Peter Bogdanoff wrote:
>>
>> Is there any particular reason a field
> On 9 Oct 2016, at 5:23 PM, Peter Bogdanoff wrote:
>
> Is there any particular reason a field, button, graphic, etc. cannot have a
> “cantDelete” property—just as stacks/cards/groups currently do have?
>
> A group can have this property set, but individual controls in that group
> cannot. If
> On 9 Oct 2016, at 4:21 PM, J. Landman Gay wrote:
>
> It's only non-obvious if you haven't been doing it for 30 years. :-)
That’s not selling it to me ;-)
Cheers
Monte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this u
Is there any particular reason a field, button, graphic, etc. cannot have a
“cantDelete” property—just as stacks/cards/groups currently do have?
A group can have this property set, but individual controls in that group
cannot. If selectGrouped is on I can accidentally delete a control. There are
It's only non-obvious if you haven't been doing it for 30 years. :-)
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 8, 2016 6:48:08 PM Monte Goulding wrote:
I suspect the fact that go sets the default
On October 8, 2016 7:06:15 PM Monte Goulding wrote:
I can’t help thinking that go touching the defaultStack at all is bug or
rather a bad idea in the first place that probably can’t be changed now.
Just because you opened a stack does not necessarily mean you want to
target the rest of your s
> On 9 Oct 2016, at 10:51 AM, Jeanne A. E. DeVoto
> wrote:
>
> OK, thar seems like a bug to me. If the only stacks open are palettes, for
> example, then go should make the target stack the topStack (and hence the
> defaultStack, since no stacks of lower mode are open).
Thinking on this some
> On 9 Oct 2016, at 10:51 AM, Jeanne A. E. DeVoto
> wrote:
>
> OK, thar seems like a bug to me. If the only stacks open are palettes, for
> example, then go should make the target stack the topStack (and hence the
> defaultStack, since no stacks of lower mode are open).
I can’t help thinking
At 10:26 AM +1100 10/9/2016, Monte Goulding wrote:
I just had a look into the source and here's the but in the go
command causing confusion:
if (t_stack->getmode() == WM_TOP_LEVEL || t_stack->getmode() ==
WM_TOP_LEVEL_LOCKED)
MCdefaultstackptr = t_stack;
What this means is that u
I suspect the fact that go sets the defaultStack (if it is topLevel) and
neither clone stack or create stack do regardless of mode also needs to be
documented somewhere. I wonder if go altering the defaultStack should be added
to the bug db as an anomaly report? It’s certainly a non-obvious side
That's what I saw too in my experiment, but I was issuing commands from the
message box. When Graham did a "go stack invisibleStack" the defaultstack
didn't change to it.
From what Monte said, I'm guessing that Graham's running script was in the
original stack and maybe the engine hadn't done
Hi Folks
I just had a look into the source and here’s the but in the go command causing
confusion:
if (t_stack->getmode() == WM_TOP_LEVEL || t_stack->getmode() ==
WM_TOP_LEVEL_LOCKED)
MCdefaultstackptr = t_stack;
What this means is that unless the mode of the stack is topLevel (1)
> On 9 Oct 2016, at 10:15 AM, Jeanne A. E. DeVoto
> wrote:
>
> (I don't claim this makes actual sense, mind you)
What about this:
go invisible stack
do some stuff depending on the defaultstack being changed to the stack
show stack
___
use-liveco
At 3:54 PM -0500 10/8/2016, J. Landman Gay wrote:
I thought visibility might impact it (I believe that's the case with
Graham's stack) so I did some quick tests and even though there was
a visible mode-1 topstack, going to the invisible one did change the
defaultstack. Thus, my curiosity.
I
> On 9 Oct 2016, at 9:09 AM, Graham Samuel wrote:
>
> Monte, thanks for that, but even your expert intervention this doesn't quite
> say what the rules actually are. I think the Dictionary should be revised to
> give a complete account.
Expert intervention might be overestimating things a bi
Monte, thanks for that, but even your expert intervention this doesn't quite
say what the rules actually are. I think the Dictionary should be revised to
give a complete account.
Cheers
Graham
Sent from my iPad
> On 8 Oct 2016, at 21:51, Monte Goulding wrote:
>
>
>> On 9 Oct 2016, at 7:22
J. Landman Gay wrote:
On 10/8/16 3:22 PM, Richard Gaskin wrote:
The rule Dr. Raney gave me is that the defaultStack is the topmost
visible stack of the lowest mode.
I thought visibility might impact it (I believe that's the case with
Graham's stack) so I did some quick tests and even though t
I have a stack that in one place and one place only when the script calls for
“ask … with … as sheet” sheets the ask dialog and then it promptly loses focus.
If I try to type a replacement for the default text or hit to affirm
the default text, nothing happens — the dialog has lost focus as one
On 10/8/16 3:22 PM, Richard Gaskin wrote:
The rule Dr. Raney gave me is that the defaultStack is the topmost
visible stack of the lowest mode.
I thought visibility might impact it (I believe that's the case with
Graham's stack) so I did some quick tests and even though there was a
visible mod
> On 9 Oct 2016, at 7:22 AM, Richard Gaskin wrote:
>
> The rule Dr. Raney gave me is that the defaultStack is the topmost visible
> stack of the lowest mode.
^ that’s pretty close but there are some other things that come into play. It’s
a bit of a slippeyr fish.
The defaultStack is set when
J. Landman Gay wrote:
> I have seen cases where the defaultstack doesn't follow the rule,
> or uses some criteria I don't understand, where "go" doesn't set
> the defaultstack automatically. I haven't yet pinned down a recipe.
> Usually I just set it by script and move on.
The rule Dr. Raney gav
On 10/8/16 10:37 AM, Dr. Hawkins wrote:
On Fri, Oct 7, 2016 at 10:50 PM, Mark Wieder wrote:
FWIW I think Jacque's explanation is the better of the two.
I think maybe LiveCode should ship her with every new build of
the dictionary.
on revBuildDictionary
clone Jacque
set the mainStack of
In Phoenix at the moment, it would be an extravagant trip!
Hope it goes well.
> On Oct 8, 2016, at 9:28 AM, Mark Schonewille
> wrote:
>
> At least one person will travel to the Netherlands. If you want to be there
> too, you're welcome. Let me know if you need help finding a hotel.
>
> I ha
At least one person will travel to the Netherlands. If you want to be there
too, you're welcome. Let me know if you need help finding a hotel.
I have no plans for a web stream, but you never know.
--
Kind regards,
Mark Schonewille
Economy-x-Talk
Http://economy-x-talk.com
Share the clipboard o
When you say this, do you mean you will have a web stream, or are you thinking
that foreign participants would fly to Utrecht that day?
> On Oct 8, 2016, at 7:44 AM, Mark Schonewille
> wrote:
>
> Sunday 16th October I will organise a meeting somewhere in the Netherlands
> (Tilburg or Utrecht
On Fri, Oct 7, 2016 at 10:50 PM, Mark Wieder wrote:
> FWIW I think Jacque's explanation is the better of the two.
> I think maybe LiveCode should ship her with every new build of
> the dictionary.
>
on revBuildDictionary
clone Jacque
set the mainStack of it to stack revDictionary
end revBui
Beste dames en heren,
Op zondag 16 oktober organiseren we een LiveCode meeting ergens in
Nederland (Tilburg of Utrecht). Het is een beetje kortdag, maar deze
datum maakt het voor een buitenlandse deelnemer mogelijk om aanwezig te
zijn. Ik hoop dat jullie op deze dag aanwezig kunnen zijn.
Het
Hi Tiemo,
is the file system set to be case sensitive and the filename of the (a) movie
in a different spelling (upper / lower case) then your player object refers to?
Cheers,
Malte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please vi
30 matches
Mail list logo
