Re: Making "read from file" less blocky.

Memory returns slowly… I take back what I said about eof maybe working for serial ports. I’m pretty sure it doesn’t. When I did this before I was taking data from 2 incoming asynchronous serial ports, one then the other then repeat. They only had tiny buffers, so I had to read small pieces of d

Re: Updated Lesson and new Notarization Helper Stack

Hats off to you again sir Matthias. Thank you On Sat, Aug 3, 2019 at 4:34 PM J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I wasn't aware of the AppWrapper update, but yours not only works > seamlessly with LC, but it's free. That's a big plus, and you're > generous

Re: Making "read from file" less blocky.

Jerry, that simple tweak worked to improve the performance of the UI a great deal.. its a slower method of loading...but not too slow to use as background loading. ...Its actually better than what I expected. Awesome. I always love to use the forever loop. its just so fun to write

Re: Making "read from file" less blocky.

Dar, Yes...I understand.it is a blocking operation no matter what I can just introduce breaks in the blockiness. So I'm not expecting a socket like experience for sure. Those are very good suggestions to try thank you. Jerry, I will give that a try, it looks promising.even a little

Re: Making "read from file" less blocky.

Hi Tom, I’ve done this in the past watching it instead of the result. I seem to remember eof was not useful. Maybe for a serial port it would be? As in: repeat forever read from file ThisFile for (1024 * 1000) bytes if it is empty then exit repeat — do your stuff wait 0 with messages end

Re: Making "read from file" less blocky.

Alas, only read from socket allows a message to be sent upon completion. The step siblings read from file, read from process and read from driver do not. Here are a few things you might do: 1. Try making the file loading very fast and don't do it in the background. Change the cursor if need be.

Making "read from file" less blocky.

Hey folks, I'm having trouble finding a combination of settings that allows my file loading to seem to happen in the background. repeat while read_result is not "eof" read from file ThisFile for (1024 * 1000) bytes put the result into read_result put it after IntoThi

Re: Updated Lesson and new Notarization Helper Stack

I wasn't aware of the AppWrapper update, but yours not only works seamlessly with LC, but it's free. That's a big plus, and you're generous to provide it to us. On 8/3/19 3:14 PM, Matthias Rebbe via use-livecode wrote: Jacque, thank you very much for your kind words. To be fair, App Wrapper 3

Re: Updated Lesson and new Notarization Helper Stack

Jacque, thank you very much for your kind words. To be fair, App Wrapper 3.9.1, which is able to notarize, was released some days ago. Regards, Matthias Matthias Rebbe free tools for Livecoders: InstaMaker WinSignMaker Mac

Re: Updated Lesson and new Notarization Helper Stack

If you need to notarize a Mac app, this thing is a marvel. I was nervous about getting through Apple's new requirements for app distribution but Notarization Helper is as simple as it gets. I'd used AppWrapper in the past, but the new notarization and stapling process isn't included there yet,

Updated Lesson and new Notarization Helper Stack

For those who are interested. Today i´ve updated the Lesson on How to code sign and Notarize an app for distribution outside of the Mac Appstore. I´ve also included an updated version of my stack. The new version is now able to to the complete stuff from code signing up to notarizing and stapli

Re: "template" stack in custom property

Hi guys, > Am 03.08.2019 um 17:19 schrieb Paul Dupuis via use-livecode > : > On 8/2/2019 10:33 PM, ambassador--- via use-livecode wrote: >> What are the advantage of instantiating the new stack from data in a prop >> rather than by cloning a substack? > That was my question too. well the first

Re: Save Standalone Settings Externally

On 8/3/19 7:53 AM, Brian Milby via use-livecode wrote: No, that is a required file for the app and needs to be in the repo. Ah. My bad. I assumed the .app was the standalone itself. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: "template" stack in custom property

On 8/2/2019 10:33 PM, ambassador--- via use-livecode wrote: What are the advantage of instantiating the new stack from data in a prop rather than by cloning a substack? That was my question too. It is a very different way of storing a stack. I imagine that an: open invisible stack (the cSav

Re: Save Standalone Settings Externally

No, that is a required file for the app and needs to be in the repo. Thanks, Brian On Aug 3, 2019, 10:40 AM -0400, Mark Wieder via use-livecode , wrote: > On 8/3/19 7:14 AM, Sannyasin Brahmanathaswami via use-livecode wrote: > > When working collaborately with a framework on Git Hub. There is alw

Re: Save Standalone Settings Externally

On 8/3/19 7:14 AM, Sannyasin Brahmanathaswami via use-livecode wrote: When working collaborately with a framework on Git Hub. There is always an issue of the stack that will be made the standalone for the app. No changes are made to binary MyMainStack.app other than settings in the standalone,

Save Standalone Settings Externally

When working collaborately with a framework on Git Hub. There is always an issue of the stack that will be made the standalone for the app. No changes are made to binary MyMainStack.app other than settings in the standalone, which you may does simply for testing. Now, if you "pull" the project