dropShadow knockout
The knockout checkbox is missing from the graphic effect dropShadow edit dialog in LC9.6.5 (Mac). The knockout property still works however. Further occasionally the edit box appear to become corrupted - after a few launches the display is out of kilter, and eventually the edit box won’t open at all (or is invisible). Not recipe for this as yet. Neville Smythe ___ 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: New MacBook Pro Display Notch
I'm not sure this will be a problem, unless you are trying to display something in the menubar, since that's where the notch is going to be. On Tue, Oct 19, 2021 at 5:14 AM Richmond via use-livecode < use-livecode@lists.runrev.com> wrote: > I should have thought the simplest way round this problem was to work on > the assumption that from now on > ALL Apple displays will have a notch and "cut one's stack" to > accommodate that. > > Of course this is only relevant to people who want to annoy end-users by > providing full-screen window apps. > > On 19.10.21 11:55, HENRY LOWE via use-livecode wrote: > > The new 14 and 16 inch MacBook Pro models announced by Apple yesterday > include a display notch to house the 1080P front facing camera. Clearly > this may cause problems for apps that display content in the screen area > occupied by the new notch. > > > > In response Apple has created a new “compatibility mode” for apps > running on Macs with a notch. When this mode is active, the system changes > the active area of the display to avoid the camera housing. This mode can > be turned on/off by the user via a checkbox in the app’s get info panel or > it can be activated or deactivated by the developer via a new ‘info.plist’ > key. > > > > Link to Apple developer documentation on how to turn on / off this mode > using the new ‘info.plist’ key is below: > > > > > https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode > > > > Henry > > > > Ascriva Health Informatics > > ___ > > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: New MacBook Pro Display Notch
I should have thought the simplest way round this problem was to work on the assumption that from now on ALL Apple displays will have a notch and "cut one's stack" to accommodate that. Of course this is only relevant to people who want to annoy end-users by providing full-screen window apps. On 19.10.21 11:55, HENRY LOWE via use-livecode wrote: The new 14 and 16 inch MacBook Pro models announced by Apple yesterday include a display notch to house the 1080P front facing camera. Clearly this may cause problems for apps that display content in the screen area occupied by the new notch. In response Apple has created a new “compatibility mode” for apps running on Macs with a notch. When this mode is active, the system changes the active area of the display to avoid the camera housing. This mode can be turned on/off by the user via a checkbox in the app’s get info panel or it can be activated or deactivated by the developer via a new ‘info.plist’ key. Link to Apple developer documentation on how to turn on / off this mode using the new ‘info.plist’ key is below: https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode Henry Ascriva Health Informatics ___ 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
New MacBook Pro Display Notch
The new 14 and 16 inch MacBook Pro models announced by Apple yesterday include a display notch to house the 1080P front facing camera. Clearly this may cause problems for apps that display content in the screen area occupied by the new notch. In response Apple has created a new “compatibility mode” for apps running on Macs with a notch. When this mode is active, the system changes the active area of the display to avoid the camera housing. This mode can be turned on/off by the user via a checkbox in the app’s get info panel or it can be activated or deactivated by the developer via a new ‘info.plist’ key. Link to Apple developer documentation on how to turn on / off this mode using the new ‘info.plist’ key is below: https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode Henry Ascriva Health Informatics ___ 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: Some questions about Command-line argument parser library
On 2021-10-18 23:04, matthias rebbe via use-livecode wrote: Mark, thank you very much for your explanations. It works now. Would you please be so kind to also explain what for the argumentArray can be used? GetOpt(grammar [, argumentArray]) Okay, i could use it for testing in the LC IDE, so i do not need to compile and execute the standalone. But is there another scenario where it would make sense to include that array in the call? It just makes it more flexible - you may need to pre-process the argument array before processing it for options - or perhaps some commands are just shorthand for others, so it allows you to separate the arguments from the thing which uses them e.g. in C, the main function passes you argv and argc, so you can in principal substitute at your leisure - indeed GetOpt() is based on the 'standard' C function getopt which does the same thing with the same grammer... The latter requires you pass in the argument array. The environment function can also return "development command line" The dictionary says about that : The stack is running in the development environment with the "-ui" command line option. So would i be able to run a stack by running the LC IDE with -ui, add the stack as parameter and add also command line options, which then could be parsed with getop()? Heh - I can't remember off the top of my head exactly what does work there - the licensed editions of LC were always a bit different from community. I did have to make some tweaks for 9.6,4 though to ensure all our build systems still run (we use LiveCode for a fair bit of stuff which occurs after the engine is built) so perhaps try it and see? :) Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps ___ 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
