Re: AW: AW: Attaching Engine - running forever
No. You need preOpen*/open*/stack, background, card, control and whatever else I forgot. Ditto all the closes. And remember to close any substacks before building or it gets worse. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 7, 2019 2:46:35 PM JJS via use-livecode wrote: I can understand. Would OpenStack or preOpenStack and closeStack not be enough to put it in? Op 7-3-2019 om 21:32 schreef J. Landman Gay via use-livecode: I wish there was a toggle for this option so we could control whether or not to lock messages. I spent way too long tracking down all the handlers I had to change (and there were lots of them,) and it's irritating to have to add that much extra code just so I can avoid a build failure. I would happily trade losing my script locals for the ability to build without errors. On 3/7/19 5:29 AM, Tiemo Hollmann TB via use-livecode wrote: Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo ___ 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
acceleratedRendering bugs
Hi, i saw there are stil 17 bugs open on acceleratedRendering. Is there any sight on when they will be solved? (or at least the most bugging ones) Especially the up shifted screen with the keyboards and the black screens (even short when switching cards) on mobile. And could it be cause for slow scrolling of DG's (with images)? I know there are some tricks, but in most cases i turn it off and on again depending what's on the card and if a keyboard has to be used. Thanks, Jerry ___ 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
Re: AW: AW: Attaching Engine - running forever
I can understand. Would OpenStack or preOpenStack and closeStack not be enough to put it in? Op 7-3-2019 om 21:32 schreef J. Landman Gay via use-livecode: I wish there was a toggle for this option so we could control whether or not to lock messages. I spent way too long tracking down all the handlers I had to change (and there were lots of them,) and it's irritating to have to add that much extra code just so I can avoid a build failure. I would happily trade losing my script locals for the ability to build without errors. On 3/7/19 5:29 AM, Tiemo Hollmann TB via use-livecode wrote: Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo ___ 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
Re: AW: AW: Attaching Engine - running forever
I wish there was a toggle for this option so we could control whether or not to lock messages. I spent way too long tracking down all the handlers I had to change (and there were lots of them,) and it's irritating to have to add that much extra code just so I can avoid a build failure. I would happily trade losing my script locals for the ability to build without errors. On 3/7/19 5:29 AM, Tiemo Hollmann TB via use-livecode wrote: Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: AW: AW: Attaching Engine - running forever
already found it:https://quality.livecode.com/show_bug.cgi?id=21881 Op 7-3-2019 om 19:16 schreef JJS via use-livecode: Hi Tiemo, great! Can you put the bugreport nr here so we can see what Panos had written? It's intereseting. Thanks! Jerry Op 7-3-2019 om 12:29 schreef Tiemo Hollmann TB via use-livecode: Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von JJS via use-livecode Gesendet: Mittwoch, 6. März 2019 19:40 An: Tiemo Hollmann TB via use-livecode Cc: JJS Betreff: Re: AW: Attaching Engine - running forever Hallo Tiemo, ok good, it was worth a try. Let's see what the devs come up with. Ciao! Jerry Op 6-3-2019 om 09:25 schreef Tiemo Hollmann TB via use-livecode: Hi Jerry, thanks for the idea. I tested it, but the result is the same. I now filed a bug report Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von JJS via use-livecode Gesendet: Dienstag, 5. März 2019 19:15 An: Tiemo Hollmann TB via use-livecode Cc: JJS Betreff: Re: Attaching Engine - running forever Hi Tiemo, maybe you need to add the piece of code which is mentioned in the release notes. You can add that piece at the top in your closestack handler. Try it if it helps. regards, Jerry Op 5-3-2019 om 11:43 schreef Tiemo Hollmann TB via use-livecode: Hello, building only a windows standalone on Win10 with LC 9.0.1/9.0.2 the standalone builder runs forever at "Attaching engine". This happens only with one of my stacks. With LC 8.1.10 the standalone builder runs fine with the same stack. 1. Is there anything I can check for? 2. The build of the exe seems to be fine (it runs). Is there anything, what is to be build after the externals folder, resources folder and the exe, or do you think I can just kill LC in this endless loop of "Attaching engine" and my standalone will be fine anyway? Thanks Tiemo ___ 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 ___ 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 ___ 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
Re: AW: AW: Attaching Engine - running forever
Hi Tiemo, great! Can you put the bugreport nr here so we can see what Panos had written? It's intereseting. Thanks! Jerry Op 7-3-2019 om 12:29 schreef Tiemo Hollmann TB via use-livecode: Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von JJS via use-livecode Gesendet: Mittwoch, 6. März 2019 19:40 An: Tiemo Hollmann TB via use-livecode Cc: JJS Betreff: Re: AW: Attaching Engine - running forever Hallo Tiemo, ok good, it was worth a try. Let's see what the devs come up with. Ciao! Jerry Op 6-3-2019 om 09:25 schreef Tiemo Hollmann TB via use-livecode: Hi Jerry, thanks for the idea. I tested it, but the result is the same. I now filed a bug report Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von JJS via use-livecode Gesendet: Dienstag, 5. März 2019 19:15 An: Tiemo Hollmann TB via use-livecode Cc: JJS Betreff: Re: Attaching Engine - running forever Hi Tiemo, maybe you need to add the piece of code which is mentioned in the release notes. You can add that piece at the top in your closestack handler. Try it if it helps. regards, Jerry Op 5-3-2019 om 11:43 schreef Tiemo Hollmann TB via use-livecode: Hello, building only a windows standalone on Win10 with LC 9.0.1/9.0.2 the standalone builder runs forever at "Attaching engine". This happens only with one of my stacks. With LC 8.1.10 the standalone builder runs fine with the same stack. 1. Is there anything I can check for? 2. The build of the exe seems to be fine (it runs). Is there anything, what is to be build after the externals folder, resources folder and the exe, or do you think I can just kill LC in this endless loop of "Attaching engine" and my standalone will be fine anyway? Thanks Tiemo ___ 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 ___ 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
Re: Compiling Livecode
No one using docker? A Linux based laptop with every application as a container has got to beat all this vmware? On Thu, 7 Mar 2019 at 07:17, Phil Davis via use-livecode < use-livecode@lists.runrev.com> wrote: > After using Parallels for a few years, I realized I hate virtual > environments. What I really do like, however, is having a Windows 10 > physical machine's desktop available in a window on my Mac, much like > Mac-to-Mac Screen Sharing. (I recently discovered MS Remote Desktop - no > going back!) I guess I could do something similar with machines running > earlier versions of Windows but haven't tried yet. > > Phil Davis > > > On 3/6/19 3:39 PM, Bob Sneidar via use-livecode wrote: > > Don't have it switch. You can share anything, or else not. You cn use > coherence view, or not. I personally like sharing my Mac environment with > my PC environment (folder redirection and all that) because it makes it > simple to collaborate between the two environments. Recently I was able to > IMPORT a VMWare VM into Parallels, becaue the VMWare player wouldn't run > the Virtual Machine I was given because it wasn't able to emulate some kind > of processor mode! ICK! I hate crap like that! > > > > Bob S > > > > > >> On Mar 6, 2019, at 03:57 , David Bovill via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> > >> Thanks Eric, I may well go that route. I've run Parallel before - but I > >> found all the switching, and space it took up a bit much. > > > > ___ > > 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 > > > > > > -- > Phil Davis > > > ___ > 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
Re: Windows: Open image with LC EXE
Hi Bob, In our case, we have a Windows app that has multiple document types. We wanted it to behave like a "real" Windows app and (1) register it's multiple documents and icons since the Standalone builder limits you to a single document type (extension) and icon; and (2) check to see if the document types have a different application as their default app and if, so, ask the user if they want our app to be associated with those file types. To use the setRegistry function in LiveCode, the process (application / EXE) must run with privileges. So we made a single stack application called Helper that is written in LiveCode that sits in a small timed loop looking for input using " read from stdin until cr" When our main app needs to change Registry settings (on startup), it use the LiveCode 'open elevated process "Helper.exe" ' command to start up the Helper.exe standalone as an elevated (or privileged) sub-process and then uses read from and write to to send messages with the registry settings as parameters and the Helper.exe updates the registry. So, for Adobe, you would need to know whether Adobe Reader supports Interprocess Communication (IPC) and if it does, what are the messages and responses (the APIs of its IPC) that it supports. Then use open process and read from process and write to process to communicate with it. On 3/6/2019 6:42 PM, Bob Sneidar via use-livecode wrote: Hi Paul. I'd be interested in how you do that. I would love to be able to tell Adobe Reader to fill a form directly (as opposed to auto-loading an .fdf file), but was under the impression you had to write some kind of C app which included the API provided by Adobe to do that. Bob S On Mar 6, 2019, at 09:13 , Paul Dupuis via use-livecode wrote: Our app ships with a separate helper app (another LC standalone/EXE) that receives instructions from the main app via interprocess ___ 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
AW: AW: Attaching Engine - running forever
Hello Jerry, your guess was good! Only in my case I had to add the same code snippet in my preopenstack and opencard handler. - Thanks to Panos for the quick solution! Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von JJS via use-livecode Gesendet: Mittwoch, 6. März 2019 19:40 An: Tiemo Hollmann TB via use-livecode Cc: JJS Betreff: Re: AW: Attaching Engine - running forever Hallo Tiemo, ok good, it was worth a try. Let's see what the devs come up with. Ciao! Jerry Op 6-3-2019 om 09:25 schreef Tiemo Hollmann TB via use-livecode: > Hi Jerry, > > thanks for the idea. I tested it, but the result is the same. I now > filed a bug report > > Tiemo > > > -Ursprüngliche Nachricht- > Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im > Auftrag von JJS via use-livecode > Gesendet: Dienstag, 5. März 2019 19:15 > An: Tiemo Hollmann TB via use-livecode > Cc: JJS > Betreff: Re: Attaching Engine - running forever > > Hi Tiemo, > > > maybe you need to add the piece of code which is mentioned in the > release notes. > > You can add that piece at the top in your closestack handler. > > Try it if it helps. > > regards, > > Jerry > > Op 5-3-2019 om 11:43 schreef Tiemo Hollmann TB via use-livecode: >> Hello, >> >> building only a windows standalone on Win10 with LC 9.0.1/9.0.2 the >> standalone builder runs forever at "Attaching engine". >> >> This happens only with one of my stacks. With LC 8.1.10 the >> standalone builder runs fine with the same stack. >> >> 1. Is there anything I can check for? >> >> 2. The build of the exe seems to be fine (it runs). Is there > anything, >> what is to be build after the externals folder, resources folder and >> the exe, or do you think I can just kill LC in this endless loop of >> "Attaching engine" and my standalone will be fine anyway? >> >> >> >> Thanks >> >> Tiemo >> >> >> >> >> >> >> >> ___ >> 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 ___ 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
