Catalina and Apple mail
Graham: before updating to Catalina definitely make a back of everything. When I updated I lost 35000 emails. Not just that they weren't loaded by Mail, they were actually deleted from the computer. That said, that was some months ago, and Catalina has since solved that problem - reportedly; I have certainly had no problems since recent OS updates. Also it is safest to do a clean instal if you can rather an update from Mojave or whatever. The experience was quite nasty. But in the process of using some LC code to recover my emails from a backup [BTW TimeMachine wouldn’t do the recovery automatically] I learnt a huge amount about mailbox structures and sqlite databases and found thousands of duplicate emails. Neville > On 18 May 2020, at 2:00 am, use-livecode-requ...@lists.runrev.com wrote: > > Send use-livecode mailing list submissions to > use-livecode@lists.runrev.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.runrev.com/mailman/listinfo/use-livecode > or, via email, send a message with subject or body 'help' to > use-livecode-requ...@lists.runrev.com > > You can reach the person managing the list at > use-livecode-ow...@lists.runrev.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of use-livecode digest..." > > > you can find the archives for this list at: > > http://lists.runrev.com/pipermail/use-livecode/ > > and search them using this link: > > http://www.google.com/advanced_search?q=site:lists.runrev.com > > > Today's Topics: > > 1. Re: Apps to fight COVID-19 (Dar Scott Consulting) > 2. Re: Sad truth about iOS apps (kee nethery) > 3. Re: Sad truth about iOS apps (Graham Samuel) > > > -- > > Message: 1 > Date: Sat, 16 May 2020 11:30:39 -0600 > From: Dar Scott Consulting > To: How to use LiveCode > Subject: Re: Apps to fight COVID-19 > Message-ID: <0e24ee6e-635f-4835-a635-14fb51258...@swcp.com> > Content-Type: text/plain; charset=us-ascii > > Covid Watch (where I'm working) is decentralized. (of course) > >> On May 14, 2020, at 10:35 AM, Mark Wieder via use-livecode >> wrote: >> >> Updated news: Germany steps up to the plate >> >> https://www.bbc.com/news/technology-52650576 >> https://github.com/corona-warn-app/cwa-documentation >> >> -- >> Mark Wieder >> ahsoftw...@gmail.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 > > > > > -- > > Message: 2 > Date: Sat, 16 May 2020 15:01:32 -0700 > From: kee nethery > To: How to use LiveCode > Subject: Re: Sad truth about iOS apps > Message-ID: <6d75b644-1acf-4279-a960-840585638...@elloco.com> > Content-Type: text/plain; charset=utf-8 > > Replaced or just deleted any 32 bit apps I had. Opened files in 32 bit apps > and converted them into something else, typically Text or PDF. Lots of files > I printed to PDF and stored the PDF versions. > > Bought some software to open MacDraw files and save them as PDF. > > I had some WriteNow files that I had to move to a really old laptop, print to > PDF, and then move back. > > All in all, I?m pretty sure that every file I now have can be viewed under > Catalina. And thus, I have migrated to Catalina. It took a bunch of time, but > hey, have lots of time right now. > > Kee > >> On May 16, 2020, at 6:40 AM, Rick Harrison via use-livecode >> wrote: >> >> For those who upgrade to Catalina, remember you will lose any 32 bit apps >> as Apple has forced everyone to move to 64 bit apps. >> >> Good luck! >> >> Rick >> >>> On May 16, 2020, at 5:42 AM, Erik Beugelaar via use-livecode >>> wrote: >>> >>> Update: You can direclty upgrade from High Sierra to Catalina using the >>> macOS Catalina Patcher. >>> Be sure that High Sierra is up-to-date and using APFS (new Apple File >>> System) instead of HFS+. >> >> ___ >> 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 > > > > > -- > > Message: 3 > Date: Sun, 17 May 2020 09:31:53 +0200 > From: Graham Samuel > To: How to use LiveCode > Subject: Re: Sad truth about iOS apps > Message-ID: <23f7cb91-5af3-47a7-bbc7-8243fcabf...@mac.com> > Content-Type: text/plain; charset=utf-8 > > There is a consistent tale (more than a rumour, I think) that Catalina can > mess up some people's mail messages, if you use Apple Mail. Did that affect > you? It?s the thing about Catalina that scares me most - after all, we?ve had > lots of warning about 32 bit apps
Re: Sad truth about iOS apps
Thanks - I hope I have the same experience as you - just bit the bullet and ordered a new iMac. Graham Sent from my iPhone > On 17 May 2020, at 18:47, Dev via use-livecode > wrote: > > No problems on two machines here with Catalina and Mail. > > Sent from my iPhone > >> On May 17, 2020, at 1:32 AM, Graham Samuel via use-livecode >> wrote: >> >> There is a consistent tale (more than a rumour, I think) that Catalina can >> mess up some people's mail messages, if you use Apple Mail. Did that affect >> you? It’s the thing about Catalina that scares me most - after all, we’ve >> had lots of warning about 32 bit apps. >> >> Graham >> On 17 May 2020, at 00:01, kee nethery via use-livecode wrote: >>> >>> Replaced or just deleted any 32 bit apps I had. Opened files in 32 bit apps >>> and converted them into something else, typically Text or PDF. Lots of >>> files I printed to PDF and stored the PDF versions. >>> >>> Bought some software to open MacDraw files and save them as PDF. >>> >>> I had some WriteNow files that I had to move to a really old laptop, print >>> to PDF, and then move back. >>> >>> All in all, I’m pretty sure that every file I now have can be viewed under >>> Catalina. And thus, I have migrated to Catalina. It took a bunch of time, >>> but hey, have lots of time right now. >>> >>> Kee >>> > On May 16, 2020, at 6:40 AM, Rick Harrison via use-livecode > wrote: For those who upgrade to Catalina, remember you will lose any 32 bit apps as Apple has forced everyone to move to 64 bit apps. Good luck! Rick > On May 16, 2020, at 5:42 AM, Erik Beugelaar via use-livecode > wrote: > > Update: You can direclty upgrade from High Sierra to Catalina using the > macOS Catalina Patcher. > Be sure that High Sierra is up-to-date and using APFS (new Apple File > System) instead of HFS+. ___ 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: LC 9.6.0 RC1 Splash/Launch Images
What I’ve done for a while is to use a flat color that is the average of the colors in the actual title screen. The splash screen is not around for very long, and with there being lots of different sizes required, a detailed splash screen could possibly take up 50 MB of app side, for the sake of a fraction of a second. In the best case it feels like the title screen faded into view. In fact, you could do that, quickly fade in from a matching flat background color. > On May 17, 2020, at 10:58 AM, panagiotis merakos via use-livecode > wrote: > > Hello Graham, > > The new storyboard mechanism has some restrictions as it is (we might > enhance it in the future) > > For example it is no longer possible to have an exact (pixel) matching of > the splash screen and the first card of the stack as it appears on the > device > > So the best suggestion now is to use a splash image that has just a logo at > the center and it is transparent, and also to set the background of the > splash in the standalone settings. > > In that way, in all devices (ipads/iphones) you will get a centered logo > with the background you set in the standalone settings (or you can choose > to not set the background - in this case the default background color will > be used depending on the device appearance: white if the device is on light > mode and black if the device is on dark mode) > > Of course, if you do not wish to have a splash that shows just a logo, you > can choose a regular image (or 3 regular images, one for each 1x,2x,3x > slots) and also set the background color to match the image background > color. In this case, depending of the device, the app will use the one of > the three images that is closer to the device screen size, and will center > this image to the screen. > > This means that the image in some devices will either match exactly, or it > will be larger (in this case it will be cropped and the edges will not > show), or it will be smaller (in this case it will be centered at the > device screen, and the left/top/right/bottom areas will show the background > color that was set in the standalone settings. > > One might ask, what size should the images be then? Well, it depends on the > images (i.e. how much content they have at the center, and if you are OK if > some of the content at the edges is cropped etc). A rule of thumb - as I > understand it - is the following: > > -use a "small", a "medium" and a "large" image for each of the 1x, 2x and > 3x slots, where "small" is the smallest image you used before the > storyboard, "large" is the largest you used before, and "medium" is > something in-between. > > For example, you could try images with these dimensions: > > - 1334x750 > - 2208x1242 (x2) > - 2732x2048 (x3) > > Hope this helps. > > We will write a lesson for this topic soon. > > Kind regards, > Panos > -- > > On Sat, 16 May 2020 at 17:49, Graham Samuel via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> This is not to answer my own question, but to emphasise the apparent >> difficulty of getting this aspect of creating an iOS app right just by >> using just LC and a reasonable graphics editor on a Mac. It means to me >> that a lot of careful instructions need to be provided by somebody in the >> LC universe, since the policy (I sincerely hope!) is to get LC developers >> to avoid getting deep into XCode. I found this, which frankly scares me. >> >> https://wiki.starling-framework.org/manual/ios_launch_images >> >> Can anyone help me to a less nerdy way of getting this right? I don’t >> even know what a storyboard is! >> >> Graham >> >>> On 16 May 2020, at 00:40, Graham Samuel via use-livecode < >> use-livecode@lists.runrev.com> wrote: >>> >>> I see that the iOS Standalone Settings have changed in this version, no >> doubt to accommodate Apple’s new rules. One is required to provide six >> images as “Launch Images” under the “Splash” tab. It seems that there’s an >> image, a 2x image and a 3x image, and then another three for dark mode. >>> >>> There is no tooltip to suggest how large these images should be - in >> previous versions they had to be tailored to different device screen sizes. >> Now it seems anything goes, or does it? >>> >>> Can anyone explain what the dimensions of these images are supposed to >> be? Does “2x” just mean twice the original size in each direction or what? >> Can’t see anything in the release notes, but maybe I wasn’t paying >> attention. >>> >>> Graham >>> ___ >>> 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: >> h
Re: LC 9.6.0 RC1 Splash/Launch Images
Hello Graham, The new storyboard mechanism has some restrictions as it is (we might enhance it in the future) For example it is no longer possible to have an exact (pixel) matching of the splash screen and the first card of the stack as it appears on the device So the best suggestion now is to use a splash image that has just a logo at the center and it is transparent, and also to set the background of the splash in the standalone settings. In that way, in all devices (ipads/iphones) you will get a centered logo with the background you set in the standalone settings (or you can choose to not set the background - in this case the default background color will be used depending on the device appearance: white if the device is on light mode and black if the device is on dark mode) Of course, if you do not wish to have a splash that shows just a logo, you can choose a regular image (or 3 regular images, one for each 1x,2x,3x slots) and also set the background color to match the image background color. In this case, depending of the device, the app will use the one of the three images that is closer to the device screen size, and will center this image to the screen. This means that the image in some devices will either match exactly, or it will be larger (in this case it will be cropped and the edges will not show), or it will be smaller (in this case it will be centered at the device screen, and the left/top/right/bottom areas will show the background color that was set in the standalone settings. One might ask, what size should the images be then? Well, it depends on the images (i.e. how much content they have at the center, and if you are OK if some of the content at the edges is cropped etc). A rule of thumb - as I understand it - is the following: -use a "small", a "medium" and a "large" image for each of the 1x, 2x and 3x slots, where "small" is the smallest image you used before the storyboard, "large" is the largest you used before, and "medium" is something in-between. For example, you could try images with these dimensions: - 1334x750 - 2208x1242 (x2) - 2732x2048 (x3) Hope this helps. We will write a lesson for this topic soon. Kind regards, Panos -- On Sat, 16 May 2020 at 17:49, Graham Samuel via use-livecode < use-livecode@lists.runrev.com> wrote: > This is not to answer my own question, but to emphasise the apparent > difficulty of getting this aspect of creating an iOS app right just by > using just LC and a reasonable graphics editor on a Mac. It means to me > that a lot of careful instructions need to be provided by somebody in the > LC universe, since the policy (I sincerely hope!) is to get LC developers > to avoid getting deep into XCode. I found this, which frankly scares me. > > https://wiki.starling-framework.org/manual/ios_launch_images > > Can anyone help me to a less nerdy way of getting this right? I don’t > even know what a storyboard is! > > Graham > > > On 16 May 2020, at 00:40, Graham Samuel via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > I see that the iOS Standalone Settings have changed in this version, no > doubt to accommodate Apple’s new rules. One is required to provide six > images as “Launch Images” under the “Splash” tab. It seems that there’s an > image, a 2x image and a 3x image, and then another three for dark mode. > > > > There is no tooltip to suggest how large these images should be - in > previous versions they had to be tailored to different device screen sizes. > Now it seems anything goes, or does it? > > > > Can anyone explain what the dimensions of these images are supposed to > be? Does “2x” just mean twice the original size in each direction or what? > Can’t see anything in the release notes, but maybe I wasn’t paying > attention. > > > > Graham > > ___ > > 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: Sad truth about iOS apps
No problems on two machines here with Catalina and Mail. Sent from my iPhone > On May 17, 2020, at 1:32 AM, Graham Samuel via use-livecode > wrote: > > There is a consistent tale (more than a rumour, I think) that Catalina can > mess up some people's mail messages, if you use Apple Mail. Did that affect > you? It’s the thing about Catalina that scares me most - after all, we’ve had > lots of warning about 32 bit apps. > > Graham > >> On 17 May 2020, at 00:01, kee nethery via use-livecode >> wrote: >> >> Replaced or just deleted any 32 bit apps I had. Opened files in 32 bit apps >> and converted them into something else, typically Text or PDF. Lots of files >> I printed to PDF and stored the PDF versions. >> >> Bought some software to open MacDraw files and save them as PDF. >> >> I had some WriteNow files that I had to move to a really old laptop, print >> to PDF, and then move back. >> >> All in all, I’m pretty sure that every file I now have can be viewed under >> Catalina. And thus, I have migrated to Catalina. It took a bunch of time, >> but hey, have lots of time right now. >> >> Kee >> On May 16, 2020, at 6:40 AM, Rick Harrison via use-livecode wrote: >>> >>> For those who upgrade to Catalina, remember you will lose any 32 bit apps >>> as Apple has forced everyone to move to 64 bit apps. >>> >>> Good luck! >>> >>> Rick >>> On May 16, 2020, at 5:42 AM, Erik Beugelaar via use-livecode wrote: Update: You can direclty upgrade from High Sierra to Catalina using the macOS Catalina Patcher. Be sure that High Sierra is up-to-date and using APFS (new Apple File System) instead of HFS+. >>> >>> ___ >>> 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: Sad truth about iOS apps
There is a consistent tale (more than a rumour, I think) that Catalina can mess up some people's mail messages, if you use Apple Mail. Did that affect you? It’s the thing about Catalina that scares me most - after all, we’ve had lots of warning about 32 bit apps. Graham > On 17 May 2020, at 00:01, kee nethery via use-livecode > wrote: > > Replaced or just deleted any 32 bit apps I had. Opened files in 32 bit apps > and converted them into something else, typically Text or PDF. Lots of files > I printed to PDF and stored the PDF versions. > > Bought some software to open MacDraw files and save them as PDF. > > I had some WriteNow files that I had to move to a really old laptop, print to > PDF, and then move back. > > All in all, I’m pretty sure that every file I now have can be viewed under > Catalina. And thus, I have migrated to Catalina. It took a bunch of time, but > hey, have lots of time right now. > > Kee > >> On May 16, 2020, at 6:40 AM, Rick Harrison via use-livecode >> wrote: >> >> For those who upgrade to Catalina, remember you will lose any 32 bit apps >> as Apple has forced everyone to move to 64 bit apps. >> >> Good luck! >> >> Rick >> >>> On May 16, 2020, at 5:42 AM, Erik Beugelaar via use-livecode >>> wrote: >>> >>> Update: You can direclty upgrade from High Sierra to Catalina using the >>> macOS Catalina Patcher. >>> Be sure that High Sierra is up-to-date and using APFS (new Apple File >>> System) instead of HFS+. >> >> ___ >> 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
