What is a stable release?
Moderator: Klaus
What is a stable release?
Am I correct thinking that a stable release should not crash on saving a stack trough script?
Trevix
OSX 14.6.1 xCode 15 LC 10 RC1 iOS 15> Android 7>
OSX 14.6.1 xCode 15 LC 10 RC1 iOS 15> Android 7>
-
- VIP Livecode Opensource Backer
- Posts: 10045
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: What is a stable release?
In any release build of any scripting language, a crash should never occur. Crashes do happen, of course, in just about all of them. But any crasher is a bug that should be reported to the vendor. With LiveCode you can report them here:
http://quality.livecode.com/
Saving stacks through script is obviously common enough that the issues affecting your project are likely specific to something in your stack file. If the stack file contains sensitive or proprietary information, just note that in the bug report and you can make arrangements to send the stack file to the team for diagnosis through confidential channels, outside of the public bug DB.
http://quality.livecode.com/
Saving stacks through script is obviously common enough that the issues affecting your project are likely specific to something in your stack file. If the stack file contains sensitive or proprietary information, just note that in the bug report and you can make arrangements to send the stack file to the team for diagnosis through confidential channels, outside of the public bug DB.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: What is a stable release?
Bug 17180 sent on middle of March
Trevix
OSX 14.6.1 xCode 15 LC 10 RC1 iOS 15> Android 7>
OSX 14.6.1 xCode 15 LC 10 RC1 iOS 15> Android 7>
Re: What is a stable release?
> Bug 17180 sent on middle of March
This bug is near the top of the list of bugs to be fixed, and has been for a while. Unfortunately there's only really one person who has the knowledge required to work on it, and he's been very busy fixing other nasty crashes and doing some other critical work.
This bug is near the top of the list of bugs to be fixed, and has been for a while. Unfortunately there's only really one person who has the knowledge required to work on it, and he's been very busy fixing other nasty crashes and doing some other critical work.
LiveCode Open Source Team — @PeterTBBrett — peter.brett@livecode.com