I just use createFolder. I discovered however that the folder you are creating
the new folder in has to exist already. In other words, if the root folder is
hdd/users/bob/documents I cannot simply create a folder
hdd/users/bob/documents/filetransfer/data/forms. I have to create file
transfer, t
Hi,
I had some trouble using revCopyFolder, maybe it is related.
Looking for a method to move/duplicate folders on MacOS I tried using
revCopyFolder.
The internal LC appleScript seems to use 'copy folder' in LC9.6.8
On MacOS 12.6.3 that does not work for me.
'duplicate folder' does.
Not sure s
You can supply the full path of a stack to the close stack command, but not to
the delete stack command. That may be worth a look by the devs.
Bob S
> On Apr 6, 2023, at 12:35, J. Landman Gay via use-livecode
> wrote:
>
> The best solution would be for LC to use file paths instead of stack
The best solution would be for LC to use file paths instead of stack names
to identify stacks. But the current implementation is so embedded in the
IDE that changing it would probably break everything. This has been
discussed quite a bit in the past but there's no easy solution.
--
Jacqueline
Sorry, I missed the first part of your post. If destroyStack/Window is true
then yes, I'd expect it to be completely removed when closed.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On April 6, 2023 1:57:40 PM Bob Sneidar via use-livec
Closing a stack is different from deleting a stack. Deleting gets rid of it
completely as you'd expect. Closing a stack removes it from view, removes
it from the message path, and does everything a deleted stack does *except*
it is kept in memory. The window structure and stack content are retai
This begs another question, how high can the id of a stack go? Presently mine
is over 33 million! (I use a lot of datagrids).
Bob S
> On Apr 6, 2023, at 11:55, Bob Sneidar via use-livecode
> wrote:
>
> I just tried to close a stack using it's full path and it did sort of, BUT...
> it only
I just tried to close a stack using it's full path and it did sort of, BUT...
it only closes the window. The Window menu in LC still shows the stack! The
destroyStack and destroyWindow properties are both true. Is that the expected
behavior???
There are of course other stacks in use, library s
I had all the same problems running through hundreds of stacks with the aim
to take snapshots of each to easily identify a stack visually. The dialog
for stacks with name conflicts always popped up. None of the methods worked
for me. But I will try again.
I have a lot of stacks with different vers
You're right, though I assumed the stack names would be sufficiently
unique. But your way is safer.
Regardless of the method, I have no idea why it isn't working for Håkan. It
should. Håkan, did you check your LC preferences in Files and Memory? Try
the various options.
--
Jacqueline Landman
In 2017 I reported a bug related to opening a series of stack files all with
the same name. The problem was that I could not get the old stacks to go away
and eventually I would end up in the “duplicate stack name” dialog infinite
loop.
https://quality.livecode.com/show_bug.cgi?id=19075
Panos
Mike.
Why a failure? i see you.
Craig
> On Apr 6, 2023, at 8:22 AM, Mike Kerner via use-livecode
> wrote:
>
> and it's a great, big, gigantic failburger
> end of line.
>
> On Tue, Apr 4, 2023 at 11:33 AM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> This is a t
Thanks for the tip! But unfortunately already tried that! I only try to work
with one stack at a time.
If I set a breakpoint and step over the line
delete stack “teststack"
And then try to open a new stack with the same name there is no dialog box
If I run the same code (without any breakpoints)
and it's a great, big, gigantic failburger
end of line.
On Tue, Apr 4, 2023 at 11:33 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> This is a test of the use list.
>
> Bob S
>
> ___
> use-livecode mailing list
> use-livecode@l
Jacque,
those two code snippets do slightly different things - and I don't think
either of them is doing exactly what's intended; I think the intent is
to delete stack(s) called (exactly) "test".
The first one will (wrongly) catch a stack called "testabc" or "abctest"
- and then will fail on
You may also be able to address this by giving any Standalone if this
app is it's own Standalone) or the Livecode version you are using the
"Full Disk Access" permission, from System Settings
On 4/6/2023 1:03 AM, Jean-Jacques Wagner via use-livecode wrote:
Hi,
Last Sunday I upgrade to ventur
16 matches
Mail list logo
