Thanks Ken. I am handing off the paths to an external application so I'll
need to convert the slashes.
Pete
On Fri, Jan 27, 2012 at 10:31 AM, Ken Ray wrote:
> So the only times we need to deal with path delimiters is when (a) working
> with the WIndows registry (see queryRegistry/setRegistry/et
On Jan 27, 2012, at 11:56 AM, Klaus on-rev wrote:
> Hi Pete,
>
> Am 27.01.2012 um 18:35 schrieb Pete:
>
>> Hi Ken,
>> You're saving my life on these Mac/Windows issues, thank you! One question
>> on this. What do the ask/answer file/folder dialogs return on Windows?
>> Does LC convert the "\"
Hi Pete,
Am 27.01.2012 um 18:35 schrieb Pete:
> Hi Ken,
> You're saving my life on these Mac/Windows issues, thank you! One question
> on this. What do the ask/answer file/folder dialogs return on Windows?
> Does LC convert the "\" chars to "/" before putting it into the it variable,
Yes!
> o
Hi Ken,
You're saving my life on these Mac/Windows issues, thank you! One question
on this. What do the ask/answer file/folder dialogs return on Windows?
Does LC convert the "\" chars to "/" before putting it into the it
variable, or just pass whatever the os returns?
Thanks,
Pete
>
> Right. I
What he said. ;-)
On Jan 27, 2012, at 7:42 AM, Ken Ray wrote:
>> My real script did have two problem but they were quite different, and might
>> be of interest.
>
> I'm glad you brought these up - for others reading this there are some "best
> practices" to learn about these things:
>
>> 1.
I remember a long time ago in a Revolution conference far, far away, someone
gave a class on good coding habits. One of the habits he mentioned was to
enclose in parenthesis where you can, partly for this reason, and partly
because it makes the code easier to read. I go halfway. If I have any do
> My real script did have two problem but they were quite different, and might
> be of interest.
I'm glad you brought these up - for others reading this there are some "best
practices" to learn about these things:
> 1. I had constructed a Windows-style path with "\" characters to fit in with
Thanks to those who replied to point out a gross stupidity on my part - the
example I gave wasn't a legal LiveCode statement. I was too tired to notice.
Sorry for the waste of bandwidth. I found the response of the message box
mysterious but at least I'll recognise it next time.
My real script
Hi Graham,
161 means "error in source expression". Probably, it is saying that "if there
is a folder (the defaultFolder)" can't be parsed into something that makes
sense, which is correct because it is only the first part of an if-then-else
control structure. If you remove the "if" then LiveCod
Graham,
The problem is you're embedding a partial 'if' structure in your statement.
Leave out the 'if':
put (there is a folder (the defaultFolder))
HTH
Devin
On Jan 26, 2012, at 3:13 PM, Graham Samuel wrote:
> I'm using LS 5.0.2. on Windows XP (OK, running under Parallels on a Mac).
> I
I'm using LS 5.0.2. on Windows XP (OK, running under Parallels on a Mac). I'm
getting unexpected results from the 'there is..' series of functions/commands -
the dictionary says they're implemented as functions, which I can understand.
As a very simple test, in the message box I put:
put (i
11 matches
Mail list logo
