Search found 9 matches
- Sun Apr 21, 2024 4:08 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Open PDF once created
- Replies: 7
- Views: 549
Re: Open PDF once created
Found the issue, I was doing something dumb passing the set widget parameter after launching browser stack. Adjusted that and working as intended. Thanks for looking.
- Sun Apr 21, 2024 3:01 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Open PDF once created
- Replies: 7
- Views: 549
Re: Open PDF once created
I should also probably mention this is for a windows standalone. It is only on other customers computers I am seeing this I believe it is because they are slower PCs. I have added a refresh button on the card so if the PDF is not loaded into the browser they can manually load it as a work around.
- Sun Apr 21, 2024 1:16 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Open PDF once created
- Replies: 7
- Views: 549
Re: Open PDF once created
Yeah I kinda thought the same thing, but how are you able to determine the creation process has finished in order to continue I guess is the question.
- Sun Apr 21, 2024 1:00 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Open PDF once created
- Replies: 7
- Views: 549
Open PDF once created
I have a process that creates a PDF then puts the output path into a new substack that has a browser widget. The problem is sometimes the PDF is still in the process of being created after the Browser substack is opened causing browser widget to fail to displaying it. Is there away to only open the ...
- Thu Sep 08, 2022 2:16 pm
- Forum: Windows
- Topic: Standalone stack file name .livecode
- Replies: 10
- Views: 6356
Re: Standalone stack file name .livecode
Your a star thank you Klaus.
- Thu Sep 08, 2022 1:46 pm
- Forum: Windows
- Topic: Standalone stack file name .livecode
- Replies: 10
- Views: 6356
Re: Standalone stack file name .livecode
Perfect thank you, just one more related question if I may. When distributing your app does exposing the albeit encrypted and password protected stack cause any security concerns. Is there any gotchas I should be aware of or is this generally a safe/secure practice.
- Thu Sep 08, 2022 12:51 pm
- Forum: Windows
- Topic: Standalone stack file name .livecode
- Replies: 10
- Views: 6356
Resolved Re: Standalone stack file name .livecode
Thanks Klaus, I like it that will work.
Just guessing as the 2nd stack is added via the add files route which means it would not be encrypted, but possibly could use an already encrypted version, will have a play.
You have already helped my many times having read previous posts so thanks again.
Just guessing as the 2nd stack is added via the add files route which means it would not be encrypted, but possibly could use an already encrypted version, will have a play.
You have already helped my many times having read previous posts so thanks again.
- Thu Sep 08, 2022 11:25 am
- Forum: Windows
- Topic: Standalone stack file name .livecode
- Replies: 10
- Views: 6356
Re: Standalone stack file name .livecode
Thanks for the response but 2 stacks that are not substacks that is not my problem but my design intention.
1st stack is launcher performs security/update tasks before launching 2nd stack main application.
1st stack is launcher performs security/update tasks before launching 2nd stack main application.
- Thu Sep 08, 2022 10:47 am
- Forum: Windows
- Topic: Standalone stack file name .livecode
- Replies: 10
- Views: 6356
Standalone stack file name .livecode
I notice that if I have windows app with say 2 top level stacks (not substacks design intention). When I create a standalone build, the primary top level stack gets merged into the exe, but the remainder stacks are named individually as stackname .livecode is there anyway to change the default file ...