On 15/12/14 17:27, Richard Gaskin wrote:
I was going to see if I could help triage these crash reports, but
going back through the posts here I was unable to turn up the one with
the bug report numbers.
If you could kindly post those I'll see if I can confirm them and do
what I can to help st
Paolo Mazza wrote:
Hi Richard ,
i think I experienced something similar.
I filed this bug and I published a video, see
http://quality.runrev.com/show_bug.cgi?id=14210
Thank you for submitting that report. Very encouraging to see that
while it was submitted only Friday, it's already marked a
Hi Richard ,
i think I experienced something similar.
I filed this bug and I published a video, see
http://quality.runrev.com/show_bug.cgi?id=14210
All the best
Paolo Mazza
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/frequent-crashes-under-7-0-1-RC3-tp468
Éric Miclo wrote:
> Bug 14218
Thank you, Éric.
Submitted this morning and confirmed within hours of your submitting the
example stack, hopefully this will be addressed in RC5.
--
Richard Gaskin
LiveCode Community Manager
rich...@livecode.org
__
Bug 14218
ÉrIC
-- My NeXT computer will Be a Mac too! --
> Le 15 déc. 2014 à 17:27, Richard Gaskin a écrit :
>
> I was going to see if I could help triage these crash reports, but going back
> through the posts here I was unable to turn up the one with the bug report
> numbers.
>
> If you
See ya.
Bob S
On Dec 14, 2014, at 08:30 , Dr. Hawkins
mailto:doch...@gmail.com>> wrote:
If I do roll back, though, it's not going to be to wait for 7, but to get
by until I figure out how to transfer my effort to another platform
entirely.
___
use-l
I was going to see if I could help triage these crash reports, but going
back through the posts here I was unable to turn up the one with the bug
report numbers.
If you could kindly post those I'll see if I can confirm them and do
what I can to help steward them through the process.
To assis
On 12/15/2014 03:01 AM, Dr. Hawkins wrote:
On Sun, Dec 14, 2014 at 11:16 AM, Richmond
wrote:
On 14/12/14 18:30, Dr. Hawkins wrote:
If I do roll back, though, it's not going to be to wait for 7, but to get
by until I figure out how to transfer my effort to another platform
entirely.
"wait
On Sun, Dec 14, 2014 at 11:16 AM, Richmond
wrote:
> On 14/12/14 18:30, Dr. Hawkins wrote:
>
>>
>>
> If I do roll back, though, it's not going to be to wait for 7, but to get
>> by until I figure out how to transfer my effort to another platform
>> entirely.
>>
>
> "wait for 7" sounds odd as we,
On 14/12/14 18:30, Dr. Hawkins wrote:
On Sun, Dec 14, 2014 at 1:17 AM, Richmond
wrote:
Well, if you must work with a release candidate I honestly don't understand
why you are surprised there are problems.
Because "release candidate" means "more than beta; we think it's good to
go, but need t
On Sun, Dec 14, 2014 at 8:23 AM, tbodine
wrote:
> Two things I found helpful:
> * Isolate LC7.x and any plug-ins, tool stacks and codebase stacks it uses
> on
> a separate user account or machine from the same resources used for LC6.
>
> I'm absolutely free of plugins and external stacks :)
And
Richard,
Sorry for your woes. I'm finding LC7 RC3 quite stable so far.
Two things I found helpful:
* Isolate LC7.x and any plug-ins, tool stacks and codebase stacks it uses on
a separate user account or machine from the same resources used for LC6.
* Be mindful of stack format versions by check
On Sun, Dec 14, 2014 at 1:17 AM, Richmond
wrote:
> Well, if you must work with a release candidate I honestly don't understand
> why you are surprised there are problems.
>
Because "release candidate" means "more than beta; we think it's good to
go, but need to confirm"--whereas livecode "releas
Hello,
> Le 14 déc. 2014 à 02:44, Dr. Hawkins a écrit :
>
> Is anyone else seeing these? I haven't had this problem with any prior
> release.
Having the same problem.
Using unicode doesn’t allow me to work with a previous version of LC.
>
> The only vaguely repeatable related event I've seen
Richmond, if you want more than a nodding acquaintance with Unicode, I think
you have to shift to the various versions of LC7. I know SOMETHING could be
done in Unicode before this, but not the things I (and I suppose many others)
wanted to do, however modest.
FWIW, none of the LC7 release can
On 12/14/2014 02:44 AM, Dr. Hawkins wrote:
Is anyone else seeing these? I haven't had this problem with any prior
release.
The only vaguely repeatable related event I've seen is that if I have an
inspector open and change a custom property, it crashes if a piece of code
tries to access that pr
16 matches
Mail list logo
