Re: OS X document icon missing
On 10/19/2023 5:37 PM, J. Landman Gay via use-livecode wrote: On 10/19/23 3:29 AM, Mark Waddingham via use-livecode wrote: The extension shouldn't have an initial `.` - I suspect that is the problem :) That was it. I had to "Get Info" on the file before Finder noticed, but then the icon showed up. I didn't even know the dot was there; I knew it shouldn't be. I someone who write a commercial software tool for researchers, I fully realize that a software vendor can not complete protect users from themselves. That said, a small Livecode enhancement might be a check if the file extension field starts with a . and either just remove it or warn the user :-) ___ 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: OS X document icon missing
On 10/19/23 3:29 AM, Mark Waddingham via use-livecode wrote: The extension shouldn't have an initial `.` - I suspect that is the problem :) That was it. I had to "Get Info" on the file before Finder noticed, but then the icon showed up. I didn't even know the dot was there; I knew it shouldn't be. -- 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: OS X document icon missing
OMG. I didn't even see that! It's my eyes, they're terrible, and getting worse as years go by. Thanks for the proofreading. Those little dots are the worst. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On October 19, 2023 3:31:18 AM Mark Waddingham via use-livecode wrote: On 2023-10-18 20:54, J. Landman Gay via use-livecode wrote: On 10/18/23 10:35 AM, Paul Dupuis via use-livecode wrote: If you have identified the document extension in the Standalone setting for macOS and set an ics file of icons (or the appropriate sizes required by Apple) than documents created by that app should display the icon. No go. Here is the relevant part of the plist: CFBundleDocumentTypes CFBundleTypeExtensions .rbox The extension shouldn't have an initial `.` - I suspect that is the problem :) Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Build Amazing Things ___ 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: Google new API 33 requirements
Hello Klaus, Thank you for the update. *So I think that was more a general warning regarding my initial app.* Ah, that should be it! Cheers, Panos On Thu, 19 Oct 2023 at 12:57, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Panos, > > > Am 19.10.2023 um 11:42 schrieb panagiotis merakos via use-livecode < > use-livecode@lists.runrev.com>: > > > > Hello Klaus, > > > > *>Does that mean I have to select -> 13 (API 33) as the * > > *Minimum Android Version in the STAB?* > > > > Nope, if you select "13 (API 33)" in the android standalone application > > settings it means your app will run only on devices that run Android 13+. > > ah, thanks for confirmation. > > > Regarding the warning/error you get from the Play Store - where (in which > > track) did you upload your new build? Was it in the Production track, or > in > > any of the (Internal/External) Testing tracks? > > My update is currently "in examination" in the Production track. > So I think that was more a general warning regarding my initial app. > > Now I have to wait for the result of the examination. > > > Could you post a screenshot of the exact warning/error you get? > > See above... > > > Also, I take it you used LiveCode 9.6.10 or 10.0.0 DP-6 to build the app, > > since these versions build against API 33 - is that correct? > > Yes LC 9.6.10. > > > Moreover, note that you do not need the "SDK Build tools v33" - you need > > "SDK Platform API 33". These are two different things. The version of the > > SDK Build tools that are installed must be 31.0.0. I believe you have the > > correct versions installed anyway, but I just mention it again to prevent > > confusion :) > > Just checked what is checked in Android Studio: > SDK platform -> Android Tiramisu (Tiramisu) -> API Level 33 > SDK Tools -> Android SDL Build-Tools 31.0.0 > Check! :-) > > Thank you for the quick answer! > > > KInd regards, > > Panos > > Best > > Klaus > > -- > Klaus Major > https://www.major-k.de > https://www.major-k.de/bass > kl...@major-k.de > > > ___ > 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: Google new API 33 requirements
Hi Panos, > Am 19.10.2023 um 11:42 schrieb panagiotis merakos via use-livecode > : > > Hello Klaus, > > *>Does that mean I have to select -> 13 (API 33) as the * > *Minimum Android Version in the STAB?* > > Nope, if you select "13 (API 33)" in the android standalone application > settings it means your app will run only on devices that run Android 13+. ah, thanks for confirmation. > Regarding the warning/error you get from the Play Store - where (in which > track) did you upload your new build? Was it in the Production track, or in > any of the (Internal/External) Testing tracks? My update is currently "in examination" in the Production track. So I think that was more a general warning regarding my initial app. Now I have to wait for the result of the examination. > Could you post a screenshot of the exact warning/error you get? See above... > Also, I take it you used LiveCode 9.6.10 or 10.0.0 DP-6 to build the app, > since these versions build against API 33 - is that correct? Yes LC 9.6.10. > Moreover, note that you do not need the "SDK Build tools v33" - you need > "SDK Platform API 33". These are two different things. The version of the > SDK Build tools that are installed must be 31.0.0. I believe you have the > correct versions installed anyway, but I just mention it again to prevent > confusion :) Just checked what is checked in Android Studio: SDK platform -> Android Tiramisu (Tiramisu) -> API Level 33 SDK Tools -> Android SDL Build-Tools 31.0.0 Check! :-) Thank you for the quick answer! > KInd regards, > Panos Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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: Google new API 33 requirements
Hello Klaus, *>Does that mean I have to select -> 13 (API 33) as the * *Minimum Android Version in the STAB?* Nope, if you select "13 (API 33)" in the android standalone application settings it means your app will run only on devices that run Android 13+. Regarding the warning/error you get from the Play Store - where (in which track) did you upload your new build? Was it in the Production track, or in any of the (Internal/External) Testing tracks? Could you post a screenshot of the exact warning/error you get? Also, I take it you used LiveCode 9.6.10 or 10.0.0 DP-6 to build the app, since these versions build against API 33 - is that correct? Moreover, note that you do not need the "SDK Build tools v33" - you need "SDK Platform API 33". These are two different things. The version of the SDK Build tools that are installed must be 31.0.0. I believe you have the correct versions installed anyway, but I just mention it again to prevent confusion :) KInd regards, Panos -- On Thu, 19 Oct 2023 at 12:04, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi friends, > > I installed the build tools for API 33 and created an update > for my app. > > In the STAB I selected : Minimum Android Version -> 8.0 > and uploaded the app to Google. > > Now I read in the Google Play Console this for my app: > ... > API Level 26+ > Target-SDK 33 > ... > However Google still shows me that my app is targeted to > Android Version 12 API 31!? > Not sure if they mean the previous version I wanted to update? > > Does that mean I have to select -> 13 (API 33) as the > Minimum Android Version in the STAB? > > If yes, is the app then still backwards-compatible with older > devices/android versions? My tablet has Android version 8.0 installed. > > Thanks for any hints! > > > Best > > Klaus > -- > Klaus Major > https://www.major-k.de > https://www.major-k.de/bass > kl...@major-k.de > > > ___ > 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
Google new API 33 requirements
Hi friends, I installed the build tools for API 33 and created an update for my app. In the STAB I selected : Minimum Android Version -> 8.0 and uploaded the app to Google. Now I read in the Google Play Console this for my app: ... API Level 26+ Target-SDK 33 ... However Google still shows me that my app is targeted to Android Version 12 API 31!? Not sure if they mean the previous version I wanted to update? Does that mean I have to select -> 13 (API 33) as the Minimum Android Version in the STAB? If yes, is the app then still backwards-compatible with older devices/android versions? My tablet has Android version 8.0 installed. Thanks for any hints! Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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: OS X document icon missing
On 2023-10-18 20:54, J. Landman Gay via use-livecode wrote: On 10/18/23 10:35 AM, Paul Dupuis via use-livecode wrote: If you have identified the document extension in the Standalone setting for macOS and set an ics file of icons (or the appropriate sizes required by Apple) than documents created by that app should display the icon. No go. Here is the relevant part of the plist: CFBundleDocumentTypes CFBundleTypeExtensions .rbox The extension shouldn't have an initial `.` - I suspect that is the problem :) Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Build Amazing Things ___ 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
