On 28/09/2013, at 4:54 AM, Jim Lambert wrote:
> With 6.1.2 RC1 setting the filename of a player to a remote URL with
> mobileControlSet will cause the app to crash in the iOS Simulator but not on
> an actual device. It plays fine.
> Setting the filename to a local file will work in both the Si
With 6.1.2 RC1 setting the filename of a player to a remote URL with
mobileControlSet will cause the app to crash in the iOS Simulator but not on an
actual device. It plays fine.
Setting the filename to a local file will work in both the Simulator and on a
device.
Anyone else seeing this?
Than
thank you, sir
--
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-livecod
thank you, sir.
On Thu, Sep 26, 2013 at 8:54 PM, Monte Goulding wrote:
> I'll get new builds of all my stuff out ASAP. I've had to make some tweaks
> to my build process but I'm nearly there.
>
> On 27/09/2013, at 10:43 AM, Mike Kerner wrote:
>
> > I'm getting a different error, with mergAES at
I'll get new builds of all my stuff out ASAP. I've had to make some tweaks to
my build process but I'm nearly there.
On 27/09/2013, at 10:43 AM, Mike Kerner wrote:
> I'm getting a different error, with mergAES attached to my project:
> linking for armv7 failed with Undefined
> symbols for archit
I'm getting a different error, with mergAES attached to my project:
linking for armv7 failed with Undefined
symbols for architecture armv7:
"___libinfoptr_mergAES", referenced from:
-u command line option
"___libinfoptr_mergZXing", referenced
from:
-u command line option
Id: symbol(s) not found fo
Hey Ralph,
That's a good spot. It looks like xCode 5 has tweaked it's code-signing
tools. LiveCode 6.1.2 will allow you to build and sign apps for armv6 or
armv7 but not when you select universal. We'll investigate.
Warm regards,
Ben
On 26 September 2013 15:59, Ralph DiMola wrote:
> I am get
I am getting this error when saving iOS standalone app.
Codesinging failed with codesign_allocate:fat file
/users/dimola/Desktop/Ralphs Stuff/JBT-Builds/JBT Red Book120/JBT Red
Book.app/JBT Red Book offset: 4096 for cputype (12) cpusubtype (6)) not
aligned on it's alignment (2^14) /Users/dimola/De
Hi Vaughn,
Thanks for the post. Based on feedback like this we've added warnings to
ensure that new users are not caught out.
Warm regards,
Ben
On 26 September 2013 15:38, Vaughn Clement wrote:
> Hi
>
> I also added the update that immediately killed the app I was working on. I
> was told th
Hi
I also added the update that immediately killed the app I was working on. I
was told the same thing that you were here, but I went back and checked the
6.5 notes and no mention of the danger was expressed. As someone new to LC
I was not pleased when my app was corrupted as soon as I re-launched
II did not ask, I just open LiveCode and a window appeared asking if I wanted
to do an update. Thinking that this update was obvious I clicked "OK" and …
Le 26 sept. 2013 à 14:53, Gerry Orkin a écrit :
> René wrote:
>
>> I don't understand ! Ihave LiveCode 6.5 (dp 1)… ???
>
> 6.5 is an experi
René wrote:
> I don't understand ! Ihave LiveCode 6.5 (dp 1)… ???
6.5 is an experimental pre-release of a version with significant changes to
many areas of the engine. You'd be mad to be running it as your day-to-day
development environment :)
Gerry
__
It’s because you’re special. Either that, or it’s because 6.5 is a developer
preview for us all to try out, whereas 6.1.2 is a release candidate, which will
become the official version if it doesn’t show any problems.
On Sep 26, 2013, at 7:04 AM, René Micout wrote:
> >I don't understand ! Iha
I don't understand ! Ihave LiveCode 6.5 (dp 1)… ???
Le 26 sept. 2013 à 12:30, Benjamin Beaumont a écrit :
> Dear List Members,
>
> We are pleased to announce the first test release of LiveCode 6.1.2. This
> is a maintenance release featuring a number of bug fixes as well as xCode 5
> support.
>
14 matches
Mail list logo
