Thanks Scott, but no luck. This might work if I was using the same url. In my case I have two urls that point to separate files. file1 is rev 1 of the stack, file1 is rev 2 of the stack. The stack inside each file has the same name, but different code.

load file1   you see version 1 of the stack
load file2   your still see version 1 of the stack

I thought about trying to see if the stack was in memory, but I am not sure to find out the name of the stack when I only have the filename.

-= Mike

On 2/16/16 1:27 PM, Scott Rossi wrote:
Try this, posted by Mike Bonner a while back:

"Like the timestamp, you can just tack on a # and the milliseconds to each
request.  http://whatever.url.com/mystack.livecode#134513461";

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 2/16/16, 10:11 AM, "use-livecode on behalf of Michael Doub"
<use-livecode-boun...@lists.runrev.com on behalf of miked...@gmail.com>
wrote:

I am building a launcher app the loads stacks from DropBox.
I am using

go URL tURL where the tURL is the stack to load using the correct
DropBox format.

This works great for the first load.  However, if I update the stack in
DropBox and try to reload tURL, it does not purge the existing stack and
load the new one.

Is there a way to force a reload?

Regards,
    Mike


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to