Re: Help with Bug #19550: Add support for symlinks to standalone builder

2018-07-21 Thread Brian Milby via use-livecode
Found something very interesting and I think it may be a bug (at least an anomaly)... if you rename a symbolic link to a folder, the folder that is pointed to is renamed vice the link consider the following (-> denotes a symbolic link) ~/tmp/ ~/tmp2 -> ./tmp/ rename "~/tmp2" "~/tmp3" results

Re: Help with Bug #19550: Add support for symlinks to standalone builder

2018-07-21 Thread Brian Milby via use-livecode
Finally working on the actual code in the IDE and discovered that there is a failure in a different spot than I thought. "there is a file" returns false on symbolic links. So my initial solution is going to need some more work. Also, file copy failures are not propagated up the call chain.

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread panagiotis merakos via use-livecode
What Jacque said; Originally you had built the standalone with LC 9.0.1 rc1 (and installed it in the device), so its manifest had targetSDKversion=26. Then you built a new one with LC 9.0.0, so it had its targetSDKversion equal to the minSDKversion, as specified in the standalone settings, and

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread J. Landman Gay via use-livecode
It could be because 9.0.1 sets the target version in the manifest to 26 and 9.0 sets it to the same version as the one you select in the dropdown menu in standalone settings. If you've truly removed the old app completely I wouldn't think it would matter, but apparently Android stores some

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread panagiotis merakos via use-livecode
Ok nice, I know what happened. I will post a detailed msg in a while as I am not in a computer now. Best, Panos On Sat, Jul 21, 2018, 21:05 Dan Friedman wrote: > Odd… I uninstalled the app from the Android phone and re-installed it. > Now it installed. Go figure. > > -Dan > > > On 7/21/18,

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread Dan Friedman via use-livecode
Odd… I uninstalled the app from the Android phone and re-installed it. Now it installed. Go figure. -Dan On 7/21/18, 12:53 PM, "use-livecode on behalf of panagiotis merakos via use-livecode" wrote: Can you try setting the app identifier in the standalone settings to something

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread panagiotis merakos via use-livecode
Can you try setting the app identifier in the standalone settings to something unique that definitely is not already installed in the device? Is it possible that you have installed an app with the same identifier (com.yourcompany.yourapp) in the device, which was built with 9.0.1 rc1? On Sat, Jul

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread panagiotis merakos via use-livecode
Hello Dan, What is the version of Android the device is running? I am wondering if you get this error because of the value of the targetSdkVersion set in the manifest. Best, Panos On Sat, Jul 21, 2018, 20:32 Ray via use-livecode < use-livecode@lists.runrev.com> wrote: > Are you having this

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread Ray via use-livecode
Are you having this problem only on other users' Macs?  If so then you've run into the same Apple induced problem I posted about a month ago.  It only happens when you distribute to others using MacOS 10.12 or higher. On 7/21/2018 2:29 PM, Dan Friedman via use-livecode wrote: So, I tried to

Re: Android, acceleratedRendering and visual effect

2018-07-21 Thread Dan Friedman via use-livecode
So, I tried to revert back to 9.0.0 because my client is pretty pissed that we’ve missed our deadline. Unfortunately, when I save as standalone in 9.0.0, and try to install it on a device, the device reports that “the package appears to be corrupt”. I tried changing the build number (as

Re: Help with Bug #19550: Add support for symlinks to standalone builder

2018-07-21 Thread Trevor DeVore via use-livecode
Brian, I can definitely test it out. I wouldn’t worry about symbolic links outside the folder right now. I don’t believe it affects .frameworks. -- Trevor DeVore On Sat, Jul 21, 2018 at 10:24 AM Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > Doing a little digging on

Re: Help with Bug #19550: Add support for symlinks to standalone builder

2018-07-21 Thread Mark Wieder via use-livecode
Brian- Here's the code I use in PowerTools to determine in a cross-platform way whether a filespec is a file or a folder. The Windows code is pretty stupid, just looking at the file extension, but I couldn't think of a better way to figure it out. HTH. /** *

Re: Help with Bug #19550: Add support for symlinks to standalone builder

2018-07-21 Thread Brian Milby via use-livecode
Doing a little digging on this. I'm pretty sure this impacts iOS in the same was as MacOS. private command __revSBCopyFolder User and group is copied if MacOS, but not Linux private command __revSBCopyFile Probably good that links are handled as files, because they technically are. Prior to

Re: adding a Shared (Background) Group after the fact

2018-07-21 Thread Tom Glod via use-livecode
thank you gentlemen! On Sat, Jul 21, 2018 at 9:37 AM, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Tom, > > > Am 21.07.2018 um 15:31 schrieb Tom Glod via use-livecode < > use-livecode@lists.runrev.com>: > > > > Hi Folks, I failed to think my stack through ahead of

Re: adding a Shared (Background) Group after the fact

2018-07-21 Thread Klaus major-k via use-livecode
Hi Tom, > Am 21.07.2018 um 15:31 schrieb Tom Glod via use-livecode > : > > Hi Folks, I failed to think my stack through ahead of time and forgot to > add a shared group to my first card before I made the other cards. > > Is there a way to do that afterwards? and have a new group shared on

Re: adding a Shared (Background) Group after the fact

2018-07-21 Thread Brian Milby via use-livecode
>From the object menu, select place group. It can be done in code if you have too many to do by hand. On Jul 21, 2018, 8:32 AM -0500, Tom Glod via use-livecode , wrote: > Hi Folks, I failed to think my stack through ahead of time and forgot to > add a shared group to my first card before I made

adding a Shared (Background) Group after the fact

2018-07-21 Thread Tom Glod via use-livecode
Hi Folks, I failed to think my stack through ahead of time and forgot to add a shared group to my first card before I made the other cards. Is there a way to do that afterwards? and have a new group shared on all the cards? Copying a shared group to existing cards doesn't seem to create an

Re: Datagrids and Nested Behaviors

2018-07-21 Thread Niggemann, Bernd via use-livecode
Bob, I also found that changing the behavior of group "dataGrid x" does not stick and after restart you have to set it again. However if you want to use the convenience of a behavior you could set in your case as far as user interaction via doubleMouseUp is concerned you could set the