Re: Supercard 4.8 public beta

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

Re: Supercard 4.8 public beta

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

Re: Pointers

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 libra

Re: lcmail.livecode saved in a newer version???

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

Re: Pasting to Powerpoint

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 mailto:h...@hyperhh.de>> wrote: On Mac there is a ClipboardViewer (https://developer.apple.com/library/content/samplecode/ClipboardViewer/) __

Re: Is 'Error Lookup' broken?

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 mailto:devin_a...@byu.edu>> wrote: The fact that scr

Re: Is 'Error Lookup' broken?

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 ___

Re: Is 'Error Lookup' broken?

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,

Re: Understanding 'the defaultStack'

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 mailto:bogdan...@me.com>> 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 t

Re: Understanding 'the defaultStack'

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

Re: Understanding 'the defaultStack'

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 y

Re: Is 'Error Lookup' broken?

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

Re: Understanding 'the defaultStack'

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 NO

Re: Is 'Error Lookup' broken?

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

Re: Is 'Error Lookup' broken?

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 li

Re: Understanding 'the defaultStack'

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 t

Re: Is 'Error Lookup' broken?

> 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

Re: Understanding 'the defaultStack'

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

Re: Understanding 'the defaultStack'

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 po

Re: Is 'Error Lookup' broken?

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 cu

Re: Understanding 'the defaultStack'

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 mailto:ambassa...@fourthwor

Re: Understanding 'the defaultStack'

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 mailto:ambassa...@fourthworld.com>> wrote: The rule Dr. Raney gave me is that the defaultStack is the top

Re: Updater doesn't update - is this correct behavior?

+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

Re: Is 'Error Lookup' broken?

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

Re: Is 'Error Lookup' broken?

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

Re: Is 'Error Lookup' broken?

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 rem

re: where files are copied to in a Mac standalone - changed in 8.1?

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

Re: Is 'Error Lookup' broken?

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

RE: Updater doesn't update - is this correct behavior?

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

Re: Close and Delete a stack

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

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 ex

Re: Passing Constants or Variables as Command Params

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

Re: Standard Icons for buttons in version 8.1 Standalones

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 pu

Re: Close and Delete a stack

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

Re: Close and Delete a stack

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 gener

Re: Close and Delete a stack

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 earlie