On 3/3/14 5:40 PM, Björnke von Gierke wrote:
I'l try to poke around a bit, I hoped someone already knew this problem :-/
Less likely these days. With the rapid rate of change in the LC engine
and the improved stability of the LC IDE in recent years, most of us
have migrated our effort from
There's still arguably a role for a lean IDE like MC as a test bed for
discerning whether a given issue encountered in LC is in the engine or the
IDE. But given the many enhancements in the engine, attempting to maintain
MC as a productive alternative delivered a lower ROI than simply
On 3/4/14 8:02 AM, Björnke von Gierke wrote:
There's still arguably a role for a lean IDE like MC as a test bed for
discerning whether a given issue encountered in LC is in the engine or the IDE.
But given the many enhancements in the engine, attempting to maintain MC as a
productive
On Feb 28, 2014, at 7:09 AM, Björnke von Gierke b...@mac.com wrote:
Hi
Yesterday I tried to use MC on windows, and it would throw a ton of errors on
any user action like opening the message box, changing the tool, etc. In
addition it was impossible to look at any scripts, because it
Thanks Ken Hugh
Maybe this is a problem with the community version somehow? I shall try the
commercial version and see if things work better there. Other then that, I
guess there's no way for me to fix it, unless i can rename the home stack and
open that in the LC IDE. Maybe I can also
Hi
Yesterday I tried to use MC on windows, and it would throw a ton of errors on
any user action like opening the message box, changing the tool, etc. In
addition it was impossible to look at any scripts, because it wouldn't actually
show the relevant scripts in the script editor window. I