LiveCode Forums.

I'll answer to myself, as it might be useful for other livecoders that could face the same error message. It turned out that in Edit -> Preferences -> Mobile Support, at "JDK path" I had to remove the path that was pointing to a JDK 8 setup that always worked fine before 9.5 AFAIK, and put the path ...

Hello LiveCoders I'm trying to do a simple test by building a "Hello world" Android app on a x86 AVD, a featured achievement on LIveCode 9.5 However, it always fails in this stage: Installation of app failed: adb: failed to install /tmp/fileuhoo4r.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES] ...

I'm happy to report that this bug has been solved in the most recent stable version available to date, which is LiveCode 8.1.2. So Linux users can now enjoy the normal feature of opening the Property Inspector for their Players, as is usual in other OSes. Edit: well, I sung victory too soon. The fix...

Jacque, It's a really good idea to branch the code in the way you showed. But I'm still in shock that such a basic IDE function such as opening the Property Inspector for a Player is not available in Linux. Yes, I'm aware that I could do the same stuff I want to do with the player by typing in the M...

Thanks for your answer mwieder. Well, I'm in shock to confirm that a basic feature (such being able to view the properties of a player) is not available for Linux users. That makes me feel like we're third class citizens in the LiveCode world, :cry: Yes, there are workarounds, but a side result of t...

Am I the only one with this issue? I drag a player into a stack. When I try to open the Player's Property Inspector, LiveCode immediately crashes. At first I thought it was some isolated issue in one computer, but soon I realized that it was happening in all my computers, 32 and 64 bits versions of ...

Hello The suggested thread was not useful, since it refers to how to solve unmet dependencies for 64 bits systems. I believe it's a bug on the 32 bit installer and not some unmet dependency, since it is able to finish without issues as "You only" setup, but it fails with the already mentioned messag...

The installation of LiveCode 8.0.0, Linux 64, all users, ran on my 64 bits system without any issue. However, I cannot say the same of the Linux 32 Installer in a 32 bit system. After typing the admin password (required for the "All users" option), a dialog appear with the message: "Installer slave ...

"Clearly from your persistence in trying to workaround the character map bug you've found, you are far more patient and tolerant of bugs than I." Ha ha ha ha, that's a good one! Well, I already reported this bug to quality.runrev.com It has the bug ID 8055. I almost thought that this bug was not sen...

Well, as I said, I had never been able to type accented characters in any version of Revolution, nor in any version of the old Metacard, so I kind of grew used to this lack as if it were something 'normal'. But, when xmodmap ceased to exist, my workaround end with it... :cry: What I'm doing now is t...

I had never been able to type accented characters in any version of Revolution or Metacard. For example, while all the other Linux apps work fine, Revolution produces 'a instead of producing the character á. I never talked about this issue because I had a workaround, I had a .Xmodmap file that let ...

Umh, I found the source of the problem. It turns out that the stacks were legacy revolution stacks. I was able to open them via "go to card x in stack y" in the IDE because in the IDE there are support for old formats, but not in the engine attached to the standalones. All I had to do was to put "Sa...

Hi fellas! I have a program that goes to a specified card in a stack. The standalone works just fine in Linux and OS X, but in Windows it does not work. The code to obtain current path of a stack is: ------------- on preOpenStack global gPath if gPath is empty then put the filename of this stack int...

Also, I posted here in order to share the workaround that worked for me, and to find if someone would have a better approach to it. And, that already happened! A user sent to my email a better solution. Instead of using: get shell("ps -ef | grep mplayer | awk '{print $2}' | xargs kill") It is easie...

Hi Bernard In order to be more precise in the report of the bug, I'd like to know if this is happening in other Rev3 Linux machines, and to know if this is only happening in the Linux version or it's a cross-platform problem. Since Mark solved a similar issue in a thread on the Mac forum, that was t...