Re: Supercard 4.8 public beta

[stephen barncard]

On Fri, Oct 14, 2016 at 9:14 PM, Bob Sneidar 
wrote:

> Filemaker has a point and click programming interface. It just gets in the
> way. I spent more time perusing the dialog and sub-dialog boxes to try and
> figure out how to add 1 to a variable that contains 1, that I found myself
> saying, "Can't I just type a formula??"
>
> I gave up on Filemaker.
>
> Bob S
>

the newest version of Numbers has awesome features that make me consider
never using Filemaker for 'simple databases' again.
especially ones that are for extended data organizers. It never got in the
way.

Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
___
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: Supercard 4.8 public beta

[Bob Sneidar]

Filemaker has a point and click programming interface. It just gets in the way. 
I spent more time perusing the dialog and sub-dialog boxes to try and figure 
out how to add 1 to a variable that contains 1, that I found myself saying, 
"Can't I just type a formula??"

I gave up on Filemaker.

Bob S


On Oct 5, 2016, at 10:22 , Richard Gaskin 
> wrote:

Like Bill Appleton told me shortly after he left his point-and-click authoring 
tool CourseBuilder behind to make SuperCard, there's a limit on the complexity 
of systems that can be expressed clearly in any point-and-click UI, and 
ultimately code becomes the more readable option for any but the most trivial 
of programs.

After all, how many point-and-click tools used their point-and-click tool to 
build their IDE? :)

Today most of the point-and-click are gone, even the industry-leading 
Authorware, while scripting language have taken over much of the world to 
dominate applications development.

--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web

___
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: Pointers

[Bob Sneidar]

When I was learning Pascal, I discovered that a handle was a pointer to a 
pointer. When I learned why that had to be, I decided to stick with Hypercard. 
:-)

Bob S


> On Oct 9, 2016, at 18:12 , JB  wrote:
> 
> Livecode has imported foundation which gives users
> the ability to access those libraries and it was written
> you can use pointers.  Pointers are used in both C &
> objective-C.  You write them a little different but the
> basic concept is the same.  A pointer points to a
> location in memory.  A variable is an object which the
> pointer points to.  If variable X holds the integer 34 &
> is located in the memory stack at 4217 the pointer will
> simply hold that address which points you to 4217 in
> memory so you can access and change the contents
> of the memory at 4217 which is the object named X
> and it is a variable of the type int or another type.
> 
> To efficiently write code using pointers you need a
> good understanding of them.  Here is a link to one
> of the best tutorials I have seen on pointers;
> 
> http://pw1.netcom.com/~tjensen/ptr/pointers.htm
> 
> This is written for beginners but it is so good even
> many advanced programmers with a good knowledge
> of pointers will benefit greatly from reading it.
> 
> JB
> 
> ___
> 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: lcmail.livecode saved in a newer version???

[Bob Sneidar]

okay lcmcil.livecode. WAIT! My speel cheecker Isnd wurknfg. rigat. 

lcmail.livecode is what I meant to type. 

Bob S


> On Oct 11, 2016, at 19:47 , Mark Wieder  wrote:
> 
> On 10/11/2016 12:14 PM, Bob Sneidar wrote:
>> I cannot open lcmcil.livecode. It says it was produced in a newer version of 
>> livecide. What is newer than 8.1.1??
> 
> Heh. livecide
> 
> -- 
> Mark Wieder
> ahsoftw...@gmail.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


___
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: Pasting to Powerpoint

[Bob Sneidar]

I clicked the link. It olly shows sample code (I assume that needs to be 
compiled??) I don't do compile. :-)

Bob S


On Oct 13, 2016, at 19:10 , hh > wrote:

On Mac there is a ClipboardViewer 
(https://developer.apple.com/library/content/samplecode/ClipboardViewer/)

___
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: Is 'Error Lookup' broken?

[Bob Sneidar]

It showed up light blue in a script, but when I right-clicked it and selected 
Find In Docs nothing happened. Then a rift opened in the space time continuum, 
and there was James Tiberius Kirk

Bob S


On Oct 14, 2016, at 09:23 , Devin Asay 
> wrote:

The fact that scriptExecutionErrors function is undocumented is a confirmed 
bug. I’m not very familiar with it, but if anyone would supply me with a simple 
description I would be happy to add it to the Dictionary on github.

Devin

___
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: Is 'Error Lookup' broken?

[Bob Sneidar]

Runs slower, but is much more fun:


Type response
Think twice
Think thrice
Go have a beer
Go have another beer
Go have a few more
Stop thinking altogether
Open computer in the morning and think, "What was I thinking?" 
Correct response
Hit send

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

Re: Is 'Error Lookup' broken?

[Bob Sneidar]

Ohhh... handy tip of the week!

Bob S


> On Oct 13, 2016, at 08:07 , Mark Wieder  wrote:
> 
> On 10/13/2016 07:30 AM, Graham Samuel wrote:
>> I should have asked as a supplementary how one might find the textual 
>> version of numerical error codes oneself, for example, I have an error
>> 
>> 347,0,0
> 
> put line 347 of the executionerrors
> 
> -- 
> Mark Wieder
> ahsoftw...@gmail.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


___
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: Understanding 'the defaultStack'

[Bob Sneidar]

That breaks Dr. Raney's rule. I'm not sure who I am anymore...

Bob S


On Oct 14, 2016, at 14:21 , Peter Bogdanoff 
> wrote:

Just tested in 8.1.1 RC 2: Two stacks open, one stack is the topStack and is 
the defaultStack.

Setting that stack’s visible to false keeps it as the defaultStack and the 
topStack.

Peter Bogdanoff

On Oct 14, 2016, at 1:37 PM, Bob Sneidar 
> wrote:

Wait what? It has to be visible? THAT I did NOT know. So hiding a stack will 
make it NOT the defaultStack if another visible stack is open.

Bob S


On Oct 8, 2016, at 13:22 , Richard Gaskin 
>
 wrote:

The rule Dr. Raney gave me is that the defaultStack is the topmost visible 
stack of the lowest mode.

___
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: Understanding 'the defaultStack'

[Bob Sneidar]

I think the more experienced devs have found ways to work around it. When in 
doubt, they use absolute references and don't depend on the engine to resolve 
relative references for them. I'm not sure if that makes your point or counters 
it. ;-)

Bob S


On Oct 14, 2016, at 14:08 , Richard Gaskin 
> wrote:

Exactly.  It must be working pretty well as it is or we would have had many 
more confused posts for decades rather than just a dozen only very recently.

--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web

___
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: Understanding 'the defaultStack'

[Graham Samuel]

Yes, but the way I think of it is if you do a ‘go’ to another stack, then the 
defaultStack changes so that you can make shorter references to objects in what 
is most likely then the current stack of interest. I got in a muddle  because 
that isn’t always true. I suppose I rubbed along for a few years before I got 
hit by that particular gotcha, so in a way Richard you’re right. Good 
documentation is probably all that’s needed, rather than trying to alter the 
engine’s behaviour.

My two Brexit-influenced, over-valued, eurocents.

Graham
> On 14 Oct 2016, at 23:08, Richard Gaskin  wrote:
> 
> Monte Goulding wrote:
> 
> >> On 15 Oct 2016, at 8:01 AM, Richard Gaskin wrote:
> >>
> >> I can't recall the last time I needed defaultStack.  It may well
> >> have been quite recently, but it must being doing what I expected
> >> it to do since I've never had to think about it before this thread.
> >
> > Every time you use an object reference that doesn’t contain an
> > explicit stack reference you are using the defaultStack. You might
> > not be getting or setting the value but you would be depending on
> > it in a large part of your code.
> 
> Exactly.  It must be working pretty well as it is or we would have had many 
> more confused posts for decades rather than just a dozen only very recently.
> 
> -- 
> 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


___
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: Is 'Error Lookup' broken?

[Monte Goulding]

> On 15 Oct 2016, at 8:15 AM, Richard Gaskin  wrote:
> 
> Dude, don't get me started on "Why is this IDE thing this way?" ;)

We accept pull requests and bribes ;-)

Cheers

Monte
___
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: Understanding 'the defaultStack'

[Peter Bogdanoff]

Just tested in 8.1.1 RC 2: Two stacks open, one stack is the topStack and is 
the defaultStack.

Setting that stack’s visible to false keeps it as the defaultStack and the 
topStack.

Peter Bogdanoff

On Oct 14, 2016, at 1:37 PM, Bob Sneidar  wrote:

> Wait what? It has to be visible? THAT I did NOT know. So hiding a stack will 
> make it NOT the defaultStack if another visible stack is open.
> 
> Bob S
> 
> 
> On Oct 8, 2016, at 13:22 , Richard Gaskin 
> > wrote:
> 
> The rule Dr. Raney gave me is that the defaultStack is the topmost visible 
> stack of the lowest mode.
> 
> ___
> 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: Is 'Error Lookup' broken?

[mwieder]

Ali-

Thanks for the correction. I was quickly just going by when the custom
properties disappeared (they're present in LC6 and LC7), not looking at the
commit log.



-
-- 
 Mark Wieder
 ahsoftw...@gmail.com
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Is-Error-Lookup-broken-tp4709348p4709408.html
Sent from the Revolution - User mailing list archive at Nabble.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: Is 'Error Lookup' broken?

[Richard Gaskin]

Monte Goulding wrote:

> I suspect what Ali found odd was setting a custom property at startup
> from an engine property didn’t make sense. I find it odd too. Better
> to use the engine property directly where needed.

Dude, don't get me started on "Why is this IDE thing this way?" ;)

I have a list of entertaining explorations in that territory, but we 
have bigger fish to fry


--
 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: Understanding 'the defaultStack'

[Richard Gaskin]

Monte Goulding wrote:

>> On 15 Oct 2016, at 8:01 AM, Richard Gaskin wrote:
>>
>> I can't recall the last time I needed defaultStack.  It may well
>> have been quite recently, but it must being doing what I expected
>> it to do since I've never had to think about it before this thread.
>
> Every time you use an object reference that doesn’t contain an
> explicit stack reference you are using the defaultStack. You might
> not be getting or setting the value but you would be depending on
> it in a large part of your code.

Exactly.  It must be working pretty well as it is or we would have had 
many more confused posts for decades rather than just a dozen only very 
recently.


--
 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: Is 'Error Lookup' broken?

[Monte Goulding]

> On 15 Oct 2016, at 7:55 AM, Richard Gaskin  wrote:
> 
> Prior to the error descriptions being added to the engine they had to be 
> somewhere, and since the error dialog was the one place they were always 
> needed putting them into a custom prop there made reasonable sense.

I suspect what Ali found odd was setting a custom property at startup from an 
engine property didn’t make sense. I find it odd too. Better to use the engine 
property directly where needed.

Cheers

Monte
___
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: Understanding 'the defaultStack'

[Monte Goulding]

> On 15 Oct 2016, at 8:01 AM, Richard Gaskin  wrote:
> 
> I can't recall the last time I needed defaultStack.  It may well have been 
> quite recently, but it must being doing what I expected it to do since I've 
> never had to think about it before this thread.

Every time you use an object reference that doesn’t contain an explicit stack 
reference you are using the defaultStack. You might not be getting or setting 
the value but you would be depending on it in a large part of your code.

Cheers

Monte
___
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: Understanding 'the defaultStack'

[Richard Gaskin]

Bob Sneidar wrote:

> Seems to me one unexpected outcome would be if you had the command
> "hide me" early in the script of a stack where another stack was
> visible, and then made references dependent on the defaultStack being
> the one hidden.

I think maybe one of the reasons we've seen more posts exploring the 
definition of defaultStack than we see complaints about its behavior is 
that in practice it's rarely needed.


I use topStack often but mostly in dev tools; in my own apps I tend to 
use custom functions to distinguish windows by semantic role rather than 
behavioral modality.


I can't recall the last time I needed defaultStack.  It may well have 
been quite recently, but it must being doing what I expected it to do 
since I've never had to think about it before this thread.


--
 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: Is 'Error Lookup' broken?

[Richard Gaskin]

Ali Lloyd wrote:

> It's not actually correct that they were introduced in LC8 --
> the properties have been there since at least 6.0.1 (
> 
https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343)

> and probably before.
>
> Previously the home stack would set the custom property of the error
> stack on startup (using the engine properties), which to my mind is
> a slightly bizarre state of affairs and I'm not sure why it was done
> that way.

Prior to the error descriptions being added to the engine they had to be 
somewhere, and since the error dialog was the one place they were always 
needed putting them into a custom prop there made reasonable sense.


--
 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: Understanding 'the defaultStack'

[Bob Sneidar]

Seems to me one unexpected outcome would be if you had the command "hide me" 
early in the script of a stack where another stack was visible, and then made 
references dependent on the defaultStack being the one hidden.

Bob S


On Oct 8, 2016, at 14:12 , Richard Gaskin 
> wrote:

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 there was a
visible mode-1 topstack, going to the invisible one did change the
defaultstack. Thus, my curiosity.

I.e.:

Stack One
visible
topstack
mode 1


command: go stack stackTwo

stackTwo
visibility false
mode 1

command: put the defaultstack
-> stackTwo


So...?

Personally I'd consider that a bug.  Even if visibility was never part of a 
formal definition, so much of the learnability of xTalk rests on being able to 
predict outcomes based on what we see.  The layering of a window visibly 
changes if a window above it becomes hidden, all the way down to how the OS 
renders the drag region.

To me it seems logical that an invisible window should be expected to require 
special handling if another window of the same mode is visible.

I can't think of a case where the behavior you've documented would be either 
anticipatable or desirable.

--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web

___
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: Understanding 'the defaultStack'

[Bob Sneidar]

Wait what? It has to be visible? THAT I did NOT know. So hiding a stack will 
make it NOT the defaultStack if another visible stack is open.

Bob S


On Oct 8, 2016, at 13:22 , Richard Gaskin 
> wrote:

The rule Dr. Raney gave me is that the defaultStack is the topmost visible 
stack of the lowest mode.

___
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: Updater doesn't update - is this correct behavior?

[Bob Sneidar]

+1 I have on several occasions downloaded the latest only to find a problem 
with it. 

Bob S


> On Oct 14, 2016, at 09:18 , Ralph DiMola  wrote:
> 
> I like to keep the older versions because of LiveCode's exciting new 
> features, multi-platform support and a faster than par update schedule to 
> support the constantly changing OS platforms. Invariably bugs (regression or 
> otherwise) creep in. I like having these older versions available by default. 
> That being said, if you click the "replace older version" box which version 
> do you overwrite if you have 4 versions(6.7.x,7.1.x,8.0.x,8.1.X) installed? 
> LiveCode being a multi platform development tool needs a different update 
> philosophy then say MS Word.
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
> Of Graham Samuel
> Sent: Friday, October 14, 2016 11:08 AM
> To: How to use LiveCode
> Subject: Updater doesn't update - is this correct behaviour?
> 
> Having updated a number of software packages on my Mac in the last couple of 
> days, I note that a typical ‘check for updates’ sequence overwrites the 
> previous version of the package: for LiveCode, this ain’t so, so one has to 
> delete the older version oneself. I guess this is OK if it’s clearly 
> explained to newbies, and there are obvious advantages if you want to go back 
> to the earlier version, but personally I would like the choice to keep or 
> replace when the installation starts. Anyone else think this is a good idea?
> 
> Graham
> ___
> 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

___
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: Is 'Error Lookup' broken?

[Ali Lloyd]

It's not actually correct that they were introduced in LC8 -- the
properties have been there since at least 6.0.1 (
https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343)
and probably before.

Previously the home stack would set the custom property of the error stack
on startup (using the engine properties), which to my mind is a slightly
bizarre state of affairs and I'm not sure why it was done that way.

On Fri, Oct 14, 2016 at 8:37 PM Devin Asay  wrote:

>
> > On Oct 14, 2016, at 1:24 PM, mwieder  wrote:
> >
> > Devin-
> >
> > Both the scriptExecutionErrors and scriptParsingErrors global properties
> are
> > currently undocumented. These contain the same lists that were formerly
> > custom properties of card 1 of the error display stack. Both properties
> were
> > introduced for the LC8 series, and the custom properties were removed at
> the
> > same time.
> >
> > The global properties contain a cr-separated list of error descriptions
> so
> > that the numeric error value returned by the engine can be used as an
> index
> > to retrieve the text.
> >
> > Examples:
> > get line 347 of the scriptExecutionErrors
> > get line 61 of the scriptParsingErrors
>
> Thanks, Mark. Here’s my first draft. Suggestions appreciated and I can
> modify it as needed.
>
> https://github.com/livecode/livecode/pull/4765
>
> Devin
>
>
> Devin Asay
> Director
> Office of Digital Humanities
> Brigham Young University
>
> ___
> 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: Is 'Error Lookup' broken?

[Devin Asay]

> On Oct 14, 2016, at 1:24 PM, mwieder  wrote:
> 
> Devin-
> 
> Both the scriptExecutionErrors and scriptParsingErrors global properties are
> currently undocumented. These contain the same lists that were formerly
> custom properties of card 1 of the error display stack. Both properties were
> introduced for the LC8 series, and the custom properties were removed at the
> same time.
> 
> The global properties contain a cr-separated list of error descriptions so
> that the numeric error value returned by the engine can be used as an index
> to retrieve the text.
> 
> Examples:
> get line 347 of the scriptExecutionErrors
> get line 61 of the scriptParsingErrors

Thanks, Mark. Here’s my first draft. Suggestions appreciated and I can modify 
it as needed.

https://github.com/livecode/livecode/pull/4765

Devin


Devin Asay
Director
Office of Digital Humanities
Brigham Young University

___
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: Is 'Error Lookup' broken?

[mwieder]

Devin-

Both the scriptExecutionErrors and scriptParsingErrors global properties are
currently undocumented. These contain the same lists that were formerly
custom properties of card 1 of the error display stack. Both properties were
introduced for the LC8 series, and the custom properties were removed at the
same time.

The global properties contain a cr-separated list of error descriptions so
that the numeric error value returned by the engine can be used as an index
to retrieve the text.

Examples:
get line 347 of the scriptExecutionErrors
get line 61 of the scriptParsingErrors

-- 
 Mark Wieder
 ahsoftw...@gmail.com




-
-- 
 Mark Wieder
 ahsoftw...@gmail.com
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Is-Error-Lookup-broken-tp4709348p4709396.html
Sent from the Revolution - User mailing list archive at Nabble.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: where files are copied to in a Mac standalone - changed in 8.1?

[Curtis Ford]

Ah OK, that makes sense. Thanks Jacque!

Curt
--
Sent from Postbox 


___
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: Is 'Error Lookup' broken?

[Devin Asay]

The fact that scriptExecutionErrors function is undocumented is a confirmed 
bug. I’m not very familiar with it, but if anyone would supply me with a simple 
description I would be happy to add it to the Dictionary on github.

Devin

> On Oct 13, 2016, at 10:51 AM, Graham Samuel  wrote:
> 
> Thanks Richard - I didn’t know how to update a plugin but I worked it out 
> (you have to delete the old one manually). Anyway very useful - thanks to you 
> and to Jacque.
> 
> Graham
> 
>> On 13 Oct 2016, at 18:01, Richard Gaskin  wrote:
>> 
>> I was mistaken:  it seems Jacque has already updated the tool to use the 
>> scriptExecutionErrors function (apparently undocumented) if the older error 
>> string list stored in stack "revErrorDisplay" is empty.
>> 
>> This should allow it to work in all versions from at least 5.5 and later.
>> 
>> Perhaps you have an older version of that stack?
>> 
>> I just added the most recent version of the LiveCode Error Lookup stack to 
>> the Stacks section of LiveNet - in the IDE see Development -> Plugins -> 
>> GoLiveNet
>> 
>> The version available there has been tested in v8.1.1 and 6.0 so it should 
>> also work with everything in between.
>> 
>> -- 
>> 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
> 
> 
> ___
> 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

Devin Asay
Director
Office of Digital Humanities
Brigham Young University

___
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: Updater doesn't update - is this correct behavior?

[Ralph DiMola]

I like to keep the older versions because of LiveCode's exciting new features, 
multi-platform support and a faster than par update schedule to support the 
constantly changing OS platforms. Invariably bugs (regression or otherwise) 
creep in. I like having these older versions available by default. That being 
said, if you click the "replace older version" box which version do you 
overwrite if you have 4 versions(6.7.x,7.1.x,8.0.x,8.1.X) installed? LiveCode 
being a multi platform development tool needs a different update philosophy 
then say MS Word.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
Graham Samuel
Sent: Friday, October 14, 2016 11:08 AM
To: How to use LiveCode
Subject: Updater doesn't update - is this correct behaviour?

Having updated a number of software packages on my Mac in the last couple of 
days, I note that a typical ‘check for updates’ sequence overwrites the 
previous version of the package: for LiveCode, this ain’t so, so one has to 
delete the older version oneself. I guess this is OK if it’s clearly explained 
to newbies, and there are obvious advantages if you want to go back to the 
earlier version, but personally I would like the choice to keep or replace when 
the installation starts. Anyone else think this is a good idea?

Graham
___
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: Close and Delete a stack

[Richard Gaskin]

Graham Samuel write:

> I have a situation where I want to close a stack and then delete it,
> so that it no  longer exists in memory and so that no naming
> conflicts occur when I load a fresh stack with the same name. This
> used to work - part of a script running in a different stack to the
> one being deleted:
>
>   set the cantDelete of stack "myDataStack" to false
>
>   set the destroyStack of stack "myDataStack" to true
>
>   set the destroyWindow of stack "myDataStack" to true
>
>   close stack "myDataStack" -- this should ensure that there are no
> messages operating in that stack
>
>   delete stack "myDataStack" -- this should remove it from memory

Here I can create a new stack, save it, then run:

   delete stack "stackname"

..in the Message Box and the stack both disappears from screen and is 
removed from the Project Browser.


One small bug:  if I then set the stack's destroyStack to true, save it, 
then close it, the Project Browser still lists it until I close and then 
re-open the PB.  That seems a bug.


But as for the script above, if that worked as shown in earlier versions 
it may be that a bug was fixed:


When I set the stack's cantDelete property to true and then try to 
delete it, I get:


   Error with "delete stack "stackname""at line 0: stack locked,
   or object's script is executing

Once I turn off the cantDelete property, the stack can then be deleted 
as expected.


--
 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

Updater doesn't update - is this correct behaviour?

[Graham Samuel]

Having updated a number of software packages on my Mac in the last couple of 
days, I note that a typical ‘check for updates’ sequence overwrites the 
previous version of the package: for LiveCode, this ain’t so, so one has to 
delete the older version oneself. I guess this is OK if it’s clearly explained 
to newbies, and there are obvious advantages if you want to go back to the 
earlier version, but personally I would like the choice to keep or replace when 
the installation starts. Anyone else think this is a good idea?

Graham
___
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: Passing Constants or Variables as Command Params

[pink]

is this your actual script? if it is, here are a few comments that
immediately pop into my mind:

1. Constants should be declared before your handler, in this case, they
should be above "on mouseUp"
2. Your "assignColor" command will not work because you are declaring those
variables as locals, they will only be available within that handler. What
you want is to declare "script locals" which need to be declared outside of
any handlers, at the top.


Try a script structured like this:

constant kPureWhite= "255,255,255" 
constant kPureBlack= "0,0,0" 
constant kDefaultStart= "0.0" # left stop 
constant kDefaultEnd= "1.0" # right stop 
constant kDefaultOpacity= "255" # 100% opaque 
constant kSoftGreen = "88,246,27" 
constant kSoftRed = "255,6,23" 

local sSoftGreen, sSoftRed 

on mouseUp 
assignColors 
setRamp "","","",sSoftRed,"",""   
end mouseup 

command assignColors
put "88,246,27" into sSoftGreen 
put "255,6,23" into sSoftRed 
end assignColors 





--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Passing-Constants-or-Variables-as-Command-Params-tp4709379p4709390.html
Sent from the Revolution - User mailing list archive at Nabble.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: Standard Icons for buttons in version 8.1 Standalones

[Bob Sneidar]

e discovered that graphics can be tricky in standalones. What I do is group a 
graphic with a button or object that uses it. I also reference the file I 
imported the graphic from in the graphic properties. I then include the folder 
with the graphic files (I keep them all in one folder for this purpose) in the 
Copy Files tab of the standalone settings. 

This has the neat effect that I can swap out button icons and background 
graphics with others of the same names as a kind of skinning feature. 

Bob S


> On Sep 11, 2016, at 18:03 , Richard Burkett  
> wrote:
> 
> When I build a standalone using LiveCode 8.1 (any version so far) the icons 
> that I have selected from the “Standard Icons” tab for button icons don’t 
> show up in the standalone. They’re there when I’m using LiveCode to open and 
> edit the stacks. Is this a bug, or are the non-resizable icons now deprecated 
> and being replaced by SVG images?
> Just wondering before I go to a lot of trouble to build new icons for a bunch 
> of things.
> 
> Richard Burkett
> richard.burk...@sbcglobal.net
> 
> 
> ___
> 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: Close and Delete a stack

[Graham Samuel]

Can any IDE experts out there explain exactly how the IDE does ‘Close and 
Remove from Memory’? I am having trouble trying to recreate this code for my 
standalone, and I am fairly sure that the code has to be different for LC8.x 
compared to earlier versions. To be clear, I’m trying to remove all trace of a 
mainstack by executing a script from within another mainstack.

TIA

Graham
___
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: Close and Delete a stack

[Graham Samuel]

Should have said, yes it’s a mainstack. I am beginning to think that the issue 
is that when I close the stack it is also purged from memory (as it says in the 
Dictionary, with provisos that I think I have obeyed), so that the following 
‘delete’ doesn’t have anything to delete - this should generate an error, but 
not 347.  

I find that if I simply cut out the ‘delete stack’ line, then everything works 
- this includes reloading a stack with the same name as the one closed, and no 
name conflict occurs. OTOH the Project Browser in the IDE claims the stack is 
still there, and an ‘exists’ enquiry returns true! Odd. The struggle now is to 
reduce this to something small enough to report as a bug.

Not sure if anyone else is interested in this, but if so, thanks for listening!

Graham

> On 14 Oct 2016, at 11:30, Graham Samuel  wrote:
> 
> Phil, thanks for the suggestion. I timed out last night and tried it this 
> morning. Strangely it didn’t work - got the same error as before (347). So 
> I’m still investigating. I am fairly sure that there is an obscure bug (or at 
> the very least, a change of behaviour) in LC 8.1.x compared to earlier 
> versions, but it is not straightforward. Onward!
> 
> Graham
> 
>> On 13 Oct 2016, at 19:32, Phil Davis  wrote:
>> 
>> Hi Graham,
>> 
>> What happens if you do only this?
>> 
>>  lock messages -- assuming you don't want any handlers to be
>>  triggered by the stack's closing
>>  delete stack "myDataStack"
>> 
>> I'm also assuming "myDataStack" is a mainStack and not a substack. (As you 
>> know, you can't remove a substack from memory independent of its mainStack 
>> unless you end its existence with "delete stack".)
>> 
>> Food for thought...
>> 
>> Phil Davis
>> 
>> 
>> 
>> On 10/13/16 10:10 AM, Graham Samuel wrote:
>>> I have a situation where I want to close a stack and then delete it, so 
>>> that it no  longer exists in memory and so that no naming conflicts occur 
>>> when I load a fresh stack with the same name. This used to work - part of a 
>>> script running in a different stack to the one being deleted:
>>> 
>>>  set the cantDelete of stack "myDataStack" to false
>>> 
>>>  set the destroyStack of stack "myDataStack" to true
>>> 
>>>  set the destroyWindow of stack "myDataStack" to true
>>> 
>>>  close stack "myDataStack" -- this should ensure that there are no messages 
>>> operating in that stack
>>> 
>>>  delete stack "myDataStack" -- this should remove it from memory
>>>  What happens in 8.1.1 rc2 (on a Mac with El Capitan, if that’s relevant) 
>>> is that all goes well until the ‘delete’ command, when I get error 347, 
>>> which is “stack locked, or object’s script executing”. Well, since the 
>>> stack is closed (this is apparent on the screen), its scripts can’t be 
>>> running, and it’s not locked (whatever that means - the dictionary is not 
>>> helpful), I don’t think the error is the correct one.
>>> 
>>> The problem exists both in the IDE and in the standalone version of the 
>>> program.
>>> 
>>> I have two problems tracking this down:
>>> 
>>> (a) it used to work up to LC7.x; and
>>> 
>>> (b) an attempt to abstract the issue by repeating it with some very simple 
>>> stacks doesn’t demonstrate the error.
>>> 
>>> Can anyone suggest an approach to debugging this?  I am totally foxed.
>>> 
>>> TIA
>>> 
>>> Graham
>>> ___
>>> 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
>> 
>> -- 
>> Phil Davis
>> 
>> ___
>> 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


___
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: Close and Delete a stack

[Graham Samuel]

Phil, thanks for the suggestion. I timed out last night and tried it this 
morning. Strangely it didn’t work - got the same error as before (347). So I’m 
still investigating. I am fairly sure that there is an obscure bug (or at the 
very least, a change of behaviour) in LC 8.1.x compared to earlier versions, 
but it is not straightforward. Onward!

Graham

> On 13 Oct 2016, at 19:32, Phil Davis  wrote:
> 
> Hi Graham,
> 
> What happens if you do only this?
> 
>   lock messages -- assuming you don't want any handlers to be
>   triggered by the stack's closing
>   delete stack "myDataStack"
> 
> I'm also assuming "myDataStack" is a mainStack and not a substack. (As you 
> know, you can't remove a substack from memory independent of its mainStack 
> unless you end its existence with "delete stack".)
> 
> Food for thought...
> 
> Phil Davis
> 
> 
> 
> On 10/13/16 10:10 AM, Graham Samuel wrote:
>> I have a situation where I want to close a stack and then delete it, so that 
>> it no  longer exists in memory and so that no naming conflicts occur when I 
>> load a fresh stack with the same name. This used to work - part of a script 
>> running in a different stack to the one being deleted:
>> 
>>   set the cantDelete of stack "myDataStack" to false
>> 
>>   set the destroyStack of stack "myDataStack" to true
>> 
>>   set the destroyWindow of stack "myDataStack" to true
>> 
>>   close stack "myDataStack" -- this should ensure that there are no messages 
>> operating in that stack
>> 
>>   delete stack "myDataStack" -- this should remove it from memory
>>   What happens in 8.1.1 rc2 (on a Mac with El Capitan, if that’s relevant) 
>> is that all goes well until the ‘delete’ command, when I get error 347, 
>> which is “stack locked, or object’s script executing”. Well, since the stack 
>> is closed (this is apparent on the screen), its scripts can’t be running, 
>> and it’s not locked (whatever that means - the dictionary is not helpful), I 
>> don’t think the error is the correct one.
>> 
>> The problem exists both in the IDE and in the standalone version of the 
>> program.
>> 
>> I have two problems tracking this down:
>> 
>> (a) it used to work up to LC7.x; and
>> 
>> (b) an attempt to abstract the issue by repeating it with some very simple 
>> stacks doesn’t demonstrate the error.
>> 
>> Can anyone suggest an approach to debugging this?  I am totally foxed.
>> 
>> TIA
>> 
>> Graham
>> ___
>> 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
> 
> -- 
> Phil Davis
> 
> ___
> 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