is the browser widget fix (or whatever change that fixes it) currently in
9dp5? or is that future branch now "behind" 8.1.4rc1?
BR
On 4/10/17, 9:32 AM, "use-livecode on behalf of Jonathan Lynch via
use-livecode" wrote:
As both Monte and Tom have suggested, moving to 8.1.4 rc 1 fixed the
As both Monte and Tom have suggested, moving to 8.1.4 rc 1 fixed the
problem for me. I am usually wary of using rc versions, but if you are
going to use a browser widget, it is probably a good idea.
On Mon, Apr 10, 2017 at 10:22 AM, Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
there was a bug in that version...try 8.14...I had the same issue...solved
now.
On Mon, Apr 10, 2017 at 5:20 AM, Jonathan Lynch via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Swami,
>
> Does your app have a browser widget?
>
> Sent from my iPhone
>
> > On Apr 10, 2017, at 12:41 AM,
Hi Swami,
Does your app have a browser widget?
Sent from my iPhone
> On Apr 10, 2017, at 12:41 AM, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> interesting I was having exactly this problem this week… slightly different
> scenario, but smells like the same fishy business.
>
> I
interesting I was having exactly this problem this week… slightly different
scenario, but smells like the same fishy business.
I was working in our branch "nightly" in 9 dp 5 and did something stupid broke
stuff… I will spare you the story.
I thought "hmm I had this working in 8.1.3" so I che
Another update
It seems to have something to do with the browser widget getting corrupted.
I copied the browser widget to a new stack and it crashed while trying to save
as a standalone.
Putting a new browser widget in the original stack did not help, but that stack
has like 6 browser widget,
> On 10 Apr 2017, at 10:58 am, Jonathan Lynch via use-livecode
> wrote:
>
> One more update - an earlier version of the app will save to a standalone.
> So, definitely something wrong with the stack. Going to try cloning the stack
> or something like that.
It sounds like attaching the stack t
One more update - an earlier version of the app will save to a standalone.
So, definitely something wrong with the stack. Going to try cloning the stack
or something like that.
Sent from my iPhone
> On Apr 9, 2017, at 8:41 PM, Monte Goulding via use-livecode
> wrote:
>
>
>> On 10 Apr 2017, a
> On 10 Apr 2017, at 10:39 am, Jonathan Lynch via use-livecode
> wrote:
>
> Not sure if I should bother with a bug report, since it is just my stack, but
> no idea how to fix my stack either.
Please do. The engine shouldn’t crash.
Cheers
Monte
___
After reinstalling and deleting the preferences file - it still does it.
It works fine for a new stack, but not for this stack.
It makes me wonder if my stack is corrupted somehow.
Wow, frustrating.
Not sure if I should bother with a bug report, since it is just my stack, but
no idea how to fi
I am reinstalling 8.1.3 - but will also delete the preferences file
Monte, if I get another crash, I will save the file.
Thanks guys
Sent from my iPhone
> On Apr 9, 2017, at 7:37 PM, Peter Bogdanoff via use-livecode
> wrote:
>
> I was working on a new Mac, and had transferred the data over f
I was working on a new Mac, and had transferred the data over from an old. I
had the same issue and had to delete the LC preferences to be able to make a
runtime.
Also, on another Mac, I sometimes get crashes when I just save a stack with a
particular external hard drive attached. The drive sta
> On 10 Apr 2017, at 9:18 am, Jonathan Lynch via use-livecode
> wrote:
>
> I had been able to save a standalone of my app on 8.1.3 on a mac, but all of
> a sudden it crashes every time.
>
> I cannot see where I changed anything in the app that would cause this. Has
> anyone else experienced
13 matches
Mail list logo
