Warning Re: 'DAZ3D is giving away three 3D-Apps for free'
jhj at jhj.com
Sat Feb 11 17:19:48 CST 2012
And it occurs to me that likely the next time I would be opening the editor would be at a remote client's location, on the clock, under pressure. Whew!
On Feb 11, 2012, at 3:09 PM, stephen barncard wrote:
> yes, Ken I made the mod too. Thanks for your observation and fix.
> On 11 February 2012 14:56, Jerry Jensen <jhj at jhj.com> wrote:
>> THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU (no dashes)
>> for bringing this up before it bit me. It would have taken me FOREVER to find the problem! Your fix worked perfectly.
>> Add one notch for keeping a recent clone backup around in addition to Time Machine.
>> Jerry Jensen
>> On Feb 11, 2012, at 2:25 PM, Ken Ray wrote:
>>> If you take advantage of downloading the DAZ3D software for Mac 64-bit computers, you need to be aware of a "gotcha":
>>> It turns out that after installing the 64-bit versions of DAZ3D on my Mac that LiveCode can't open a script editor window anymore. This turned out to be because it inserted two "bad" environment variables: ($DAZSTUDIOVERSION_4-64 and $DAZSTUDIO_4-64) which LC would error out on when trying to work with global variables. The "-" in these globals is what did it…
>>> So if you've installed these and find yourself in a situation trying to open a script window and seeing nothing but "revNewScriptEditor 1" in the Windows menu, you'll need to either (a) wait until RunRev fixes it, (b) find another copy of LC on another machine or install the MetaCard IDE and then edit the revDebugger.rev file (in Contents/Tools/Toolset), go to the "revDebuggerValidGlobalNames" function and change it to add:
>>> filter tGlobalsRaw without "*-*"
> Stephen Barncard
> San Francisco Ca. USA
> more about sqb
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode