Re: RELEASE LiveCode 6.6 DP1

On 23/02/14 20:48, Bob Sneidar wrote: My problem is trying to get the cat to STOP dressing up in drag when I’m not around. Obviously it is trying to ASSERT itself, and OFFSET some of the negative aspects of living with you: Next thing you know it will be Skipping Characters :) Bob On F

Re: RELEASE LiveCode 6.6 DP1

My problem is trying to get the cat to STOP dressing up in drag when I’m not around. Bob On Feb 23, 2014, at 10:10 , Richmond wrote: > On 23/02/14 20:08, Bob Sneidar wrote: >> But whatever you do, do NOT attempt to take the cat on a long walk after >> getting him intoxicated while listening

Re: RELEASE LiveCode 6.6 DP1

On 23/02/14 20:08, Bob Sneidar wrote: But whatever you do, do NOT attempt to take the cat on a long walk after getting him intoxicated while listening to a long symphony. First, the cat is likely not going to go very far if you try to walk him, and secondly alcohol is poison to cats. If you do

Re: RELEASE LiveCode 6.6 DP1

But whatever you do, do NOT attempt to take the cat on a long walk after getting him intoxicated while listening to a long symphony. First, the cat is likely not going to go very far if you try to walk him, and secondly alcohol is poison to cats. If you don’t believe me and attempt this, your wa

Re: RELEASE LiveCode 6.6 DP1

>> So my suggestion would be to update errorDialog, maybe make a synonym for >> people used to other languages. And then add an assert control structure (or >> even just modify try to be able to use it in that way). I would not like having this.; they are 2 different beasts and concepts. ( And

Re: RELEASE LiveCode 6.6 DP1

Alright I think I've said what I wanted on assert, so my next problem is with the SQLite syntax changes. The "new" binary mode is in fact just the default SQLite way to use binary. Because of that, I strongly would prefer to make that the default, and deprecate the LC way of storing binary in

Re: RELEASE LiveCode 6.6 DP1

On 21.02.2014, at 16:36, Björnke von Gierke wrote: > So my suggestion would be to update errorDialog, maybe make a synonym for > people used to other languages. And then add an assert control structure (or > even just modify try to be able to use it in that way). -- Use an alternative Dict

Re: RELEASE LiveCode 6.6 DP1

On 23/02/14 13:43, Thierry Douez wrote: I still think that adding an assert command (of all things) is a completely wrong way to do that tho. Well, everybody is entitled to their own opinion. One of the things I really, really like about Livecode, is the way that there are many ways to do the

Re: RELEASE LiveCode 6.6 DP1

>> I still think that adding an assert command (of all things) is a >> completely wrong way to do that tho. and Dilbert to the rescue: http://dilbert.com/dyn/str_strip/0//000/20/1//900/210948/210948.strip.zoom.gif Have a nice sunday :) Thierry

Re: RELEASE LiveCode 6.6 DP1

Björnke von Gierke wrote: > I still think that adding an assert command (of all things) is a > completely wrong way to do that tho. What i'd want is this to use > existing capabilities, instead of sidestepping how things work right > now. Maybe a control structure would be a lot more in touch wit

Re: RELEASE LiveCode 6.6 DP1

Hi Bjornke, I just tried a simple assert/assertError. If the assert fails, the commands in the assertError message handler are executed then the original handler still continues to execute, so assert exits the handler to the assertError message handler , then goes back to the original handler. Pe

Re: RELEASE LiveCode 6.6 DP1

I'm not really "warming up" to the syntax. I'm warming up to the idea, but I like Björnke's thinking on this. One of the things that's been bugging me is that this reminds me of try/catch, but it's not thought-out enough, yet. On Fri, Feb 21, 2014 at 10:36 AM, Björnke von Gierke wrote: > Alri

Re: RELEASE LiveCode 6.6 DP1

Alright, thanks everyone for explaining this. I see now that assert does something that existing capabilities didn't do: Make your own errors up. I still think that adding an assert command (of all things) is a completely wrong way to do that tho. What i'd want is this to use existing capabiliti

Re: RELEASE LiveCode 6.6 DP1

Mark Wieder wrote: >> To bring this new feature to completion I just added a request for a >> global property to turn it off: >> >> AllowAssert global property >> > > Comment added to bug report. > > Richard: if you don't explicitly put in an asse

Re: RELEASE LiveCode 6.6 DP1

> For example, you may want asserts to be evaluated during testing, but > not in the final product. > > To bring this new feature to completion I just added a request for a > global property to turn it off: > > AllowAssert global property > Com

Re: RELEASE LiveCode 6.6 DP1

Hi Bjornke, Like you, I'm still skeptical about how useful this really is. I'm sensing that LC coders who also work with other more traditional programming languages will be more comfortable with assert. To answer your question though, one example might be a parameter to a function which is always

Re: RELEASE LiveCode 6.6 DP1

Björnke von Gierke wrote: > On 20.02.2014, at 16:37, Richard Gaskin wrote: > >> The key point there is that both only catch things the engine >> considers errors. >> >> Assert compliments those by providing for things which may be >> syntactically correct and completely executable, yet are errors

Re: RELEASE LiveCode 6.6 DP1

I think a nice example stack (perhaps even closer to a final release) put onto revOnline would help everyone. I'd love to know more about this upcoming feature. On Thu, Feb 20, 2014 at 10:51 AM, Björnke von Gierke wrote: > > On 20.02.2014, at 16:37, Richard Gaskin > wrote: > > > The key point

RE: RELEASE LiveCode 6.6 DP1

Subject: Re: RELEASE LiveCode 6.6 DP1 On 20.02.2014, at 16:37, Richard Gaskin wrote: > The key point there is that both only catch things the engine considers errors. > > Assert compliments those by providing for things which may be syntactically correct and completely executable, yet a

Re: RELEASE LiveCode 6.6 DP1

On 20.02.2014, at 16:37, Richard Gaskin wrote: > The key point there is that both only catch things the engine considers > errors. > > Assert compliments those by providing for things which may be syntactically > correct and completely executable, yet are errors within the context of the > b

Re: RELEASE LiveCode 6.6 DP1

Björnke von Gierke wrote: > On 16.02.2014, at 22:13, Peter Haworth wrote: > >> Seems like it's really meant to detect the >> infamous "this should never happen" situation rather than expected >> errors., > > Alright, if that is the case, why isn't it done in the engine WITHOUT > adding another c

Re: RELEASE LiveCode 6.6 DP1

On 16.02.2014, at 22:13, Peter Haworth wrote: > Seems like it's really meant to detect the > infamous "this should never happen" situation rather than expected errors., Alright, if that is the case, why isn't it done in the engine WITHOUT adding another command? why do WE need to add random c

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 2/16/14, 2:19 PM, Bob Sneidar wrote: To Mark’s point, turning off SSID broadcasting is really only to keep the less-than-adept from jumping on your wireless. It really does nothing these days to secure your wireless. Neither does Mac Address Filtering by the way. Yeah, I'd read that so I did

Re: RELEASE LiveCode 6.6 DP1

Thanks for the explanation Mark. Been prowling around the web for information on assert and I think I'm getting clearer on its use. Seems like it's really meant to detect the infamous "this should never happen" situation rather than expected errors., kinda like a switch default statement to show

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 16/02/14 20:13, Mark Wieder wrote: Richmond- Sunday, February 16, 2014, 12:54:21 AM, you wrote: So; I got into my TP-LINK router's settings and changed the DNS to one of the ones I mentioned in an earlier posting: had to physically restart the router (the soft restart just stopped the thing

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

To Mark’s point, turning off SSID broadcasting is really only to keep the less-than-adept from jumping on your wireless. It really does nothing these days to secure your wireless. Neither does Mac Address Filtering by the way. Tools exist that can mimic your Mac Address, which can be discerned b

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

Pretty sure you can change the primary DNS on ALL devices, but you really are going about it properly by changing the DNS on the router instead. Wait until the monkeys are gone, then do as you please with the router. Bob On Feb 16, 2014, at 24:15 , Richmond mailto:richmondmathew...@gmail.com>

Re: RELEASE LiveCode 6.6 DP1

Okay so that means there is corruption in DNS. No surprisingly, since I have a Sprint WiFi cell data dongle which won’t work or work well when I use the default DNS, but when I switch to Google DNS it starts working famously. Another possible cause would be DNS cacheing. Changing the DNS settin

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

Jacque- Sunday, February 16, 2014, 11:24:46 AM, you wrote: > On 2/16/14, 12:13 PM, Mark Wieder wrote: >> And turn off SSID broadcast - you'll have to type the SSID >> manually in order to connect the first time, but it will keep your >> router under the radar. >> > I had broadcasting turned off

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 2/16/14, 12:13 PM, Mark Wieder wrote: And turn off SSID broadcast - you'll have to type the SSID manually in order to connect the first time, but it will keep your router under the radar. I had broadcasting turned off for years and wanted to keep it that way, but as soon as I got an Androi

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

Richmond- Sunday, February 16, 2014, 12:54:21 AM, you wrote: > So; I got into my TP-LINK router's settings and changed the DNS to one > of the ones I mentioned in an earlier posting: > had to physically restart the router (the soft restart just stopped the > thing working) as well as the cable mo

Re: RELEASE LiveCode 6.6 DP1

Pete- Sunday, February 16, 2014, 9:11:23 AM, you wrote: > All valid points. I'm just not seeing any big advantages over using if/then > constructs, but I can see that being a personal preference. Well, one advantage of assert is that the parameters pinpoint exactly where the error occurred, maki

Re: RELEASE LiveCode 6.6 DP1

All valid points. I'm just not seeing any big advantages over using if/then constructs, but I can see that being a personal preference. Pete lcSQL Software On Feb 16, 2014 4:49 AM, "Trevor DeVore" wrote: > On Sunday, February 16, 2014, Peter Haworth wrote: > > > The assert command seems to have

Re: RELEASE LiveCode 6.6 DP1

On Sunday, February 16, 2014, Peter Haworth wrote: > The assert command seems to have appeared out of nowhere. Is it on any > plan that anyone has seen? I believe it was added in order to aid with adding test coverage to LiveCode. At least I seem to recall reading something about that in some

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 16/02/14 10:17, Richmond wrote: On 16/02/14 10:15, Richmond wrote: On 15/02/14 22:12, Mark Wieder wrote: Richmond- Saturday, February 15, 2014, 11:43:37 AM, you wrote: and "bingo", everything is lovely. Yay! Well "semi-bingo" insofar as individual computers can now bypass the router'

Re: [OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 16/02/14 10:15, Richmond wrote: On 15/02/14 22:12, Mark Wieder wrote: Richmond- Saturday, February 15, 2014, 11:43:37 AM, you wrote: and "bingo", everything is lovely. Yay! Well "semi-bingo" insofar as individual computers can now bypass the router's DNS setting (all the Linux boxes I

[OT] Richmond's DNS disease, was: RELEASE LiveCode 6.6 DP1

On 15/02/14 22:12, Mark Wieder wrote: Richmond- Saturday, February 15, 2014, 11:43:37 AM, you wrote: and "bingo", everything is lovely. Yay! Well "semi-bingo" insofar as individual computers can now bypass the router's DNS setting (all the Linux boxes I have connected to my router), but o

Re: RELEASE LiveCode 6.6 DP1

The assert command seems to have appeared out of nowhere. Is it on any plan that anyone has seen? Anyway, with assert: - --Test Harness using assert - command test1 assert . end test1 command test2 assert . end test2 on

Re: RELEASE LiveCode 6.6 DP1

On Sat, Feb 15, 2014 at 5:24 PM, Björnke von Gierke wrote: > Can someone elaborate why assert is better then using "is true/false", and > what additional things it adds? > 'assert' is designed for writing tests for your code. That being the case, if 'assert' fails then the assertError message is

Re: RELEASE LiveCode 6.6 DP1

Bjornke, That was my question exactly. On Sat, Feb 15, 2014 at 5:24 PM, Björnke von Gierke wrote: > Can someone elaborate why assert is better then using "is true/false", and > what additional things it adds? > > I don't feel i can do the following otherwise: "Please do not be afraid to > try i

Re: RELEASE LiveCode 6.6 DP1

Can someone elaborate why assert is better then using "is true/false", and what additional things it adds? I don't feel i can do the following otherwise: "Please do not be afraid to try it out as we need feedback to develop it further." (page 7, http://downloads.livecode.com/livecode/6_6_0/Live

Re: RELEASE LiveCode 6.6 DP1

Richmond- Saturday, February 15, 2014, 11:43:37 AM, you wrote: > and "bingo", everything is lovely. Yay! -- -Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscri

Re: RELEASE LiveCode 6.6 DP1

On 15/02/14 21:30, Mark Wieder wrote: Richmond- Hmmm... possible dns resolution issues? Can you ping www.livecode.com ? If not, can you ping 37.59.205.89 ? You might also try reconfiguring your dns settings to point to Google's dns servers at 8.8.8.8 to see if that helps. pinging 37.59.205.8

Re: RELEASE LiveCode 6.6 DP1

On Sat, Feb 15, 2014 at 11:04 AM, Richmond wrote: > Anyway; obviously nothing wrong with RunRev, and quite a lot with my ISP > over here: both in terms of their service, and > in terms of the fact that their people talk unmitigated rubbish. > Sadly, not an unusual situation. It seems many suppor

Re: RELEASE LiveCode 6.6 DP1

Richmond- Hmmm... possible dns resolution issues? Can you ping www.livecode.com ? If not, can you ping 37.59.205.89 ? You might also try reconfiguring your dns settings to point to Google's dns servers at 8.8.8.8 to see if that helps. -- -Mark Wieder ahsoftw...@gmail.com

Re: RELEASE LiveCode 6.6 DP1

On 15/02/14 20:48, Klaus major-k wrote: Am 15.02.2014 um 19:45 schrieb Jim Kanter : All links okay in Atlanta, GA. Same over here in germany! :-) I have just had a majorly stupid conversation with an 'engineer' from my ISP provider who told me this: 1. Maybe the Livecode people have blo

Re: RELEASE LiveCode 6.6 DP1

All links OK here in Mexico City, too On 15 Feb 2014, at 12:48 PM, Klaus major-k wrote: > > Am 15.02.2014 um 19:45 schrieb Jim Kanter : > >> All links okay in Atlanta, GA. > > Same over here in germany! :-) > >> On Sat, Feb 15, 2014 at 11:08 AM, Richmond >> wrote: >>> >>> here in Bulg

Re: RELEASE LiveCode 6.6 DP1

Am 15.02.2014 um 19:45 schrieb Jim Kanter : > All links okay in Atlanta, GA. Same over here in germany! :-) > On Sat, Feb 15, 2014 at 11:08 AM, Richmond > wrote: >> >> here in Bulgaria, and they told me that they cannot connect to >> downloads.livecode.com/livecode/ >> or lists.runrev.com: s

Re: RELEASE LiveCode 6.6 DP1

All links okay in Atlanta, GA. On Sat, Feb 15, 2014 at 11:08 AM, Richmond wrote: > > here in Bulgaria, and they told me that they cannot connect to > downloads.livecode.com/livecode/ > or lists.runrev.com: so something going on there. > > At the moment I cannot, also, connect with > http://andre

Re: RELEASE LiveCode 6.6 DP1

Me too! And I’m in Brooklyn! So, quite a range of coverage here in the States. On Feb 15, 2014, at 12:50 PM, PystCat wrote: > >If it helps, I can access all of those links here in NY city. ___ use-livecode mailing list use-livecode@lists.runrev.com P

Re: RELEASE LiveCode 6.6 DP1

If it helps, I can access all of those links here in NY city. Paul > On Feb 15, 2014, at 11:08 AM, Richmond wrote: > >> On 15/02/14 17:07, Marc Van Cauwenberghe wrote: >> Hi, >> >> the url seems to be alright to me. >> >> Any news on the sample stacks? >> >> Best regards, >> Marc > > I phon

Re: RELEASE LiveCode 6.6 DP1

On 15/02/14 17:07, Marc Van Cauwenberghe wrote: Hi, the url seems to be alright to me. Any news on the sample stacks? Best regards, Marc I phoned the engineers at BLIZOO, http://en.wikipedia.org/wiki/Blizoo here in Bulgaria, and they told me that they cannot connect to downloads.liveco

Re: RELEASE LiveCode 6.6 DP1

Bug 11814 This bug is caused by setting acceleratedRendering to true On 2/14/14, 5:06 PM, "Michael Gruenthal" wrote: >Just ran a stable in 6.5 iPad (1024 X 768) stack in the iOS 7 retina >simulator. As is, it is scaled down to occupy the bottom left quarter of >the simulator screen, but all obj

Re: RELEASE LiveCode 6.6 DP1

Hi, the url seems to be alright to me. Any news on the sample stacks? Best regards, Marc Op 15-feb.-2014, om 12:48 heeft Richmond het volgende geschreven: > On 14/02/14 20:05, Benjamin Beaumont wrote: >> Dear List Members. >> >> We are pleased to announce the release of LiveCode 6.6 DP1. >>

Re: RELEASE LiveCode 6.6 DP1

On 14/02/14 20:05, Benjamin Beaumont wrote: Dear List Members. We are pleased to announce the release of LiveCode 6.6 DP1. Warning, this is a pre-release with new features which have the potential to cause issues. Please ensure you backup your stacks before testing this release. *Important Cha

Re: RELEASE LiveCode 6.6 DP1

Don't worry, Peter, I won't. I will speak up when something comes in that makes me go UGH, though. "this me" and the new "assert" syntax also come to mind. On Fri, Feb 14, 2014 at 5:11 PM, Peter Haworth wrote: > So don't use it then :-) I'm happy to see SQLite catching up with other > SQL im

Re: RELEASE LiveCode 6.6 DP1

So don't use it then :-) I'm happy to see SQLite catching up with other SQL implementations. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Fri, Feb 14, 2014 at 1:06 PM, Mike

Re: RELEASE LiveCode 6.6 DP1

Just ran a stable in 6.5 iPad (1024 X 768) stack in the iOS 7 retina simulator. As is, it is scaled down to occupy the bottom left quarter of the simulator screen, but all objects are actually where they belong e.g. touching a button where it¹s rendered in the bottom left quarter doesn't work, but

Re: RELEASE LiveCode 6.6 DP1

Great. A 25 year step BACKWARDS when it comes to readability. There is nothing readable about recursive code. It might be clever and brief, but it is most definitely NOT readable. On Fri, Feb 14, 2014 at 2:22 PM, Peter Haworth wrote: > I see in the release notes that the hope is to include t

Re: RELEASE LiveCode 6.6 DP1

LiveCode use-livecode@lists.runrev.com Subject:  Re: RELEASE LiveCode 6.6 DP1 On Feb 14, 2014, at 11:05 AM, Benjamin Beaumont wrote: > *Sample Stacks* > We have included 3 sample stack demonstrating some of the new > features/improvements in this release: > - Stack showing effec

Re: RELEASE LiveCode 6.6 DP1

On Feb 14, 2014, at 11:05 AM, Benjamin Beaumont wrote: > *Sample Stacks* > We have included 3 sample stack demonstrating some of the new > features/improvements in this release: > - Stack showing effect of changes in image quality > - Stack showing effect of fullscreenmode on desktop > - Stack s

Re: RELEASE LiveCode 6.6 DP1

I see in the release notes that the hope is to include the 3.8.3 version of the SQLite library in the final release of 6.6. One of the very cool new features in sqlite 3.8.3 is recursive SELECT statements. Think expanding a bill of materials or a manager/employee chart with one SELECT statement.

Re: RELEASE LiveCode 6.6 DP1

On Fri, Feb 14, 2014 at 10:05 AM, Benjamin Beaumont wrote: > - SQLite support updated and improved YES Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin _

Re: RELEASE LiveCode 6.6 DP1

Im sure there are some people very excited about the sqlite update. Very cool. On Fri, Feb 14, 2014 at 12:05 PM, Benjamin Beaumont wrote: > Dear List Members. > > We are pleased to announce the release of LiveCode 6.6 DP1. > > Warning, this is a pre-release with new features which have the pote

RELEASE LiveCode 6.6 DP1

Dear List Members. We are pleased to announce the release of LiveCode 6.6 DP1. Warning, this is a pre-release with new features which have the potential to cause issues. Please ensure you backup your stacks before testing this release. *Important Changes* 1. *Tiger support dropped*. As of ve