Search found 23 matches
- Wed Aug 17, 2022 7:52 pm
- Forum: Talking LiveCode
- Topic: Windows 11 Help
- Replies: 51
- Views: 18956
Re: Windows 11 Help
Like WebiWan *some* of my clients are reporting this error involving Print.PrintSupport.Source.dll in Windows 10 ... very sporadic ... very annoying since I CANNOT reproduce the issue on ANY Windows 10 platform I have access to. Has anyone, beyond the discussions in this stream have any further info...
- Thu Nov 19, 2020 8:25 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Re: Standalone compile never leaves closing open stacks
Fantastic!!! This solved all of the compile problems I was having ... I'm very happy about now being able to use the latest version of LC. However... one question remains... If this code is REQUIRED in those sorts of handlers... why leave it to the developer to REMEMBER to specify it when the Standa...
- Thu Nov 19, 2020 6:07 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Wndows 10 desktop issue
- Replies: 3
- Views: 2983
Re: Wndows 10 desktop issue
Thanks very much ... questionable feature ... I wish all my problems were THIS easy. Why one default for Windows 7 and another for Windows 10? ... Whatever... thanks again!
- Wed Nov 18, 2020 10:01 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Wndows 10 desktop issue
- Replies: 3
- Views: 2983
Wndows 10 desktop issue
Why do I get all the weird issues??? While attempting to resolve a compile issue (see: "Standalone compile never leaves closing open stacks" in this forum), I've found that all versions of LC (from 8.1.10 to 9.6.1) COMPLETELY take over my desktop on Windows 10 pro 64 bit platforms and set the backgr...
- Wed Nov 18, 2020 8:41 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Re: Standalone compile never leaves closing open stacks
Here's an "interesting" bit of additional info regarding the standalone compile. I mentioned that v8.1.10 works perfectly. Well, I decided to try to see if I could find a v9x version which DID work. I already determined that the newest version (v9.6.1) exhibits this issue for me.... and I had also t...
- Tue Nov 17, 2020 6:18 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Re: Standalone compile never leaves closing open stacks
if you're referring to the following from release notes on v9.0.0: on closeStack if the mode of stack "revStandaloneProgress" > 0 then exit closesStack end if end closeStack yes ... kind-of ... since I don't use the "closeStack" handler specifically, I did try this in the button which actually close...
- Tue Nov 17, 2020 6:34 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Re: Standalone compile never leaves closing open stacks
Thanks again for the input. On the two stacks which compiled to the "Attach Engine" stage and then froze, I did have "lock messages" within the handler I use to exit the app .. although I don't use the "on closeStack" handler... but simply on a button: on mouseUp --lock messages set the destroyStack...
- Mon Nov 16, 2020 6:29 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Re: Standalone compile never leaves closing open stacks
Thank you both for your replies... regarding searching for "standalone" ... ?too common? ... Really? Particularly when the term is a reference to a LIVECODE function ... I tried many variations (e.g. in quotes, case variations, etc... I'm no amateur in searching for things). I also tried "compile" b...
- Mon Nov 16, 2020 6:34 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: Standalone compile never leaves closing open stacks
- Replies: 20
- Views: 9610
Standalone compile never leaves closing open stacks
First... it's hard to understand why the term "Standalone" is *ignored* in this forum's search since it is a term used by Livecode itself... go figure! Using Livecode 9.5.0 build 15503 on Windows 7 enterprise 64 bit. Set the Standalone Application settings to only a Windows build (tried BOTH Windows...
- Fri Apr 13, 2018 4:31 pm
- Forum: MergEXT
- Topic: Re-Initialising mergBLE
- Replies: 1
- Views: 5626
Re: Re-Initialising mergBLE
Kudos to support@livecode.com for providing the solution I was seeking. Here is their response to my posting (although it was sent directly to them via email): ========== start of livecode response ================== The mergBLEInitialize command just initializes the library, it doesn't cause any co...
- Fri Apr 13, 2018 5:34 am
- Forum: MergEXT
- Topic: Re-Initialising mergBLE
- Replies: 1
- Views: 5626
Re-Initialising mergBLE
I have been in contact with forum user: "bwmilby" who has helped me on some aspects of my problems with mergBLE... much appreciated!!... but this one "problem" remains and I desperately need to get it resolved. I am submitting this forum entry on the direct advice of Monte Goulding, the developer of...
- Fri Apr 13, 2018 5:33 am
- Forum: Engine Contributors
- Topic: disconnect and re-connect to MergBLE
- Replies: 8
- Views: 14148
Re: disconnect and re-connect to MergBLE
I'd like to move this continuing discussion to the MergExt forum upon the advice of Monte Goulding... please see the subject "Re-Initialising mergBLE" in that forum
Doug
Doug
- Fri Apr 13, 2018 3:27 am
- Forum: Engine Contributors
- Topic: disconnect and re-connect to MergBLE
- Replies: 8
- Views: 14148
Re: disconnect and re-connect to MergBLE
yes, as discovered on the other thread, I have "fixed" the "checkFrom" handle to use the "wait with messages" syntax... that works fine now. You are right (of course) why the "version" of "doNoACK" I presented doesn't work... I actually do know NOT to use a "message" handler as a "command"... stupid...
- Wed Aug 17, 2016 7:17 pm
- Forum: Android Deployment
- Topic: no JDK path after newest Android Studio & Jave SE El Capitan
- Replies: 1
- Views: 2834
Re: no JDK path after newest Android Studio & Jave SE El Cap
so... here's the "answer" from LC support... and I sincerely hope the next person who goes looking for this "solution" finds this posting first and saves themselves several hours of frustration: "... LiveCode, generally, is happy with newer versions of Java (i.e it works on non-MacOS systems) howeve...
- Mon Aug 15, 2016 6:54 pm
- Forum: Android Deployment
- Topic: no JDK path after newest Android Studio & Jave SE El Capitan
- Replies: 1
- Views: 2834
no JDK path after newest Android Studio & Jave SE El Capitan
I have searched the FAQ's and forum for an answer to this issue but cannot find one. After installing the latest version of Android Studio (2.1.2) and Java 8 (/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk) on a MAC running El Capitan ...LC v8.0.2 will NOT populate the JDK path in the LC Mobile ...