On 12/17/2019 2:51 AM, Mark Waddingham via use-livecode wrote:
On 2019-12-15 13:29, Paul Dupuis via use-livecode wrote:
Just a reminder that the files(,"detailed") (i.e. the detailed
files) and the detailed folders are NOT Unicode aware. If you have any
Unicode characters in path or the file
On 2019-12-15 13:29, Paul Dupuis via use-livecode wrote:
Just a reminder that the files(,"detailed") (i.e. the detailed
files) and the detailed folders are NOT Unicode aware. If you have any
Unicode characters in path or the file names, they will be returned as
URLEncoded question marks making
I came to this conclusion over a year ago and have had refactoring away from it
on the back burner. No longer. I went through my code and divorced myself from
this addictive coding habit.
Bob S
> On Dec 16, 2019, at 09:15 , Mark Waddingham via use-livecode
> wrote:
>
> Upshot - never use
On 2019-12-16 16:54, J. Landman Gay via use-livecode wrote:
On launch, the defaultfolder is set to the folder containing the
executable. On desktop this is the folder containing livecode. In a
standalone it's the folder containing the app (which on Mac is inside
the bundle.) But any time you
On launch, the defaultfolder is set to the folder containing the
executable. On desktop this is the folder containing livecode. In a
standalone it's the folder containing the app (which on Mac is inside the
bundle.) But any time you change the defaultfolder it stays there, it
doesn't set
Thanks for the info! I hope you solve the problem.
JB
> On Dec 16, 2019, at 7:55 AM, Bob Sneidar via use-livecode
> wrote:
>
> Thanks JB. Getting and setting the default folder was not the issue. The
> issue is that in a wondows standalone, a stack in the same folder as the
> executable
Thanks JB. Getting and setting the default folder was not the issue. The issue
is that in a wondows standalone, a stack in the same folder as the executable
could not be opened by script eg. open stack "Devices". This seems to be a new
development, as I am fairly certain this worked fine in the
Oh sweet thanks.
Bob S
> On Dec 14, 2019, at 17:33 , Alex Tweedly via use-livecode
> wrote:
>
>>>
>>> On Dec 13, 2019, at 3:21 PM, Bob Sneidar via use-livecode
>>> wrote:
>>>
>>> Thanks for the confirmation Tom. I did see two places in my code that I
>>> have to set the default folder,
On 12/14/2019 8:33 PM, Alex Tweedly via use-livecode wrote:
On Dec 13, 2019, at 3:21 PM, Bob Sneidar via use-livecode
wrote:
Thanks for the confirmation Tom. I did see two places in my code
that I have to set the default folder, so I just reset it when I am
done. Same thing, getting list
On Dec 13, 2019, at 3:21 PM, Bob Sneidar via use-livecode
wrote:
Thanks for the confirmation Tom. I did see two places in my code that I have to
set the default folder, so I just reset it when I am done. Same thing, getting
list of files. There may have been some discussion in the past
I am not using Windows or the version of Livecode you are
using so I am not testing this but when it comes to using
paths you might want to make sure what path is being
provided.
If the path returned includes a file name then it might
not work properly for listing that directory because it
is
If you know the path you need then put this code in
your stack;
answer question effective filename of this stack
answer question defaultFolder
after creating the standalone run the code above from
the app and see if either of the paths provided are the
path you are actually trying to use.
Thanks for the confirmation Tom. I did see two places in my code that I have to
set the default folder, so I just reset it when I am done. Same thing, getting
list of files. There may have been some discussion in the past about a files
command where the path could be passed, but that's not
I only use defaultfolder when I need to get a list of files in that
folder. Otherwise its the kind of thing that comes back to haunt us
for no real reason.
On Fri, Dec 13, 2019 at 12:07 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Not sure. There have been
Not sure. There have been threads in the past relating to the defaultFolder,
and how it can in certain cases cause other issues, so I think my strategy for
avoiding setting the defaultFolder is the way to go. I've been meaning to for a
while now. I just wanted to alert everyone in case they run
Would the stackfiles property help here?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 13, 2019 10:33:38 AM Bob Sneidar via use-livecode
wrote:
Hi all.
I was given to understand that in a standalone, when I open another
Hi all.
I was given to understand that in a standalone, when I open another stack it by
default looks in the folder the executable is in first, and then in some other
places if it doesn't find it. This used to work and now does not. When for
instance I issue the command "go stack devices"
17 matches
Mail list logo
