Beware! GTX2 can cause problems

Jerry Daniels jerry at daniels-mara.com
Tue Mar 18 13:12:34 EDT 2008


Thanks, Len. We actually use the beta product here for client projects  
and other commercial development, so it's very useable.

I do have to say one more thing:

I think it would be better to avoid the alarmist headlines like  
"Beware! GTX2 can cause problems". It just might be we are the by- 
product of life of headlines from the news, etc.

Wouldn't it would be nice--as engineers--if we could be somewhat  
factual and proportionate in our posting titles which stay around  
forever and go into the Akashic Record (Google)?

"Script save problem: GLX2 or Rev?" might be a better, more accurate  
call for help.

My two cents.

Best,

Jerry Daniels

Daniels & Mara, Inc.
Makers of GLX2
http://www.daniels-mara.com/glx2



On Mar 18, 2008, at 11:40 AM, Len Morgan wrote:

> I will add one final comment to this thread:
>
> Daniels & Mara's Betas are better (and less buggy) that a lot of  
> commercial released and "stable" software!  Some might contend that  
> using the term "beta" when referring to GLX2, while accurate, is  
> doing a disservice to other "beta" software because it tends to  
> raise expectations.  Perhaps "beta plus" would be better.  :-)
>
> len morgan
>
> Jerry Daniels wrote:
>> Marian,
>>
>> I couldn't agree more. This discussion does belong on the site  
>> devoted to the subject. Out of respect for other people's time, if  
>> nothing else.
>>
>> If you're not signed up for GLX2 support yet (and you are a  
>> currently licensed user), let me know and we'll add you to the site.
>>
>> Best,
>>
>> Jerry Daniels
>>
>> Daniels & Mara, Inc.
>> Makers of GLX2
>> http://www.daniels-mara.com/glx2
>>
>>
>>
>> On Mar 18, 2008, at 10:38 AM, Marian Petrides, M.D. wrote:
>>
>>> One quick suggestion if I might offer it.... if this appears to be  
>>> an isolated problem with a beta version of GLX2, maybe we should  
>>> retire this discussion to the Daniel-Mara site.
>>> The reason I suggest this is that previous negative comments about  
>>> Galaxy (years ago) had kept me from installing GLX2 for months  
>>> after I bought it as part of the Christmas bundle.  Then several  
>>> very positive comments last week finally caused me to work up the  
>>> courage to install it--which I wish I had done a long time ago.
>>>
>>> Thusfar, it hasn't caused any problems (I'm using 2.0.2 not a 2.1  
>>> beta) and it is so much easier to use (ability to see code for  
>>> multiple objects at once is just GREAT!).
>>>
>>> I'd hate to think that our discussions here about a _beta_ might  
>>> scare others away from using this very helpful tool. Just a  
>>> thought...  I'll go back to lurking now.
>>>
>>> M
>>>
>>>
>>> On Mar 18, 2008, at 9:46 AM, Len Morgan wrote:
>>>
>>>> Believe me Jerry, I have (for the most part) gotten over my prior  
>>>> tendency toward immediate condemnation of GLX (and Galaxy before  
>>>> that, and Constellation before that) whenever anything goes flaky  
>>>> with Rev.  I was merely saying that in a similar situation to  
>>>> Dave's it happened on or around the time I uninstalled the beta,  
>>>> went back to the stable version, then back to the beta again.
>>>>
>>>> When I watch the Windows Task Manager, it is Revolution that is  
>>>> taking 60-100% of the CPU time so I'm not sure where else to  
>>>> look.  Perhaps there has been some sort of Windows update that  
>>>> doesn't show up in the TaskManager.  GLX is still usable,
>>>> just slow at times.
>>>>
>>>> len morgan
>>>>
>>>>
>>>> Jerry Daniels wrote:
>>>>> Len, there are quite a few people using that version without  
>>>>> that problem or anything like it. Many of us use GLX2 many hours  
>>>>> a day, day after day. One wonders what it is about your system  
>>>>> that's causing it. Memory? Some specific to your machine?
>>>>>
>>>>> On Mar 18, 2008, at 7:50 AM, Len Morgan wrote:
>>>>>
>>>>>> 2.1b40
>>>>>>
>>>>>> Petrides, M.D. Marian wrote:
>>>>>>> Which beta were you using when you had problems?
>>>>>>>
>>>>>>> On Mar 18, 2008, at 7:37 AM, Len Morgan wrote:
>>>>>>>
>>>>>>>> I've started having the same problem: Massive slow down of  
>>>>>>>> the whole system when I've got GLX2 running.  This was after  
>>>>>>>> deleting the preferences file.  To try and solve another  
>>>>>>>> problem, I was advised to go back to the stable version.   
>>>>>>>> After the problem had been resolved, I went back to the  
>>>>>>>> latest beta and that's when the slow down started.  Sometimes  
>>>>>>>> it gets to the point of being almost unusable.
>>>>>>>>
>>>>>>>> len morgan
>>>>>>>>
>>>>>>>> Dave wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> It doesn't appear to be doing that on my system, also it  
>>>>>>>>> started running so slowly so as it be unusable, so I  
>>>>>>>>> uninstalled it. Spent a weird hour trying to figure out  
>>>>>>>>> where my changes had got to last night!
>>>>>>>>>
>>>>>>>>> All the Best
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>> On 17 Mar 2008, at 14:28, Trevor DeVore wrote:
>>>>>>>>>
>>>>>>>>>> On Mar 17, 2008, at 5:35 AM, Dave wrote:
>>>>>>>>>>
>>>>>>>>>>> Ran into this and it caused me no end of grief, I'm using  
>>>>>>>>>>> two versions of RunRev, 2.8.1.472 and the 2.9 Beta. I also  
>>>>>>>>>>> use GTX2 and this is where the confusion came in. If you  
>>>>>>>>>>> edit a script in one version of RunRev/GTX2, then open the  
>>>>>>>>>>> Script in the version of RunRev/GTX2, the changes don't  
>>>>>>>>>>> appear! I think that GTX2 must be caching the Script  
>>>>>>>>>>> Source code somewhere that is Private to the Version of  
>>>>>>>>>>> RunRev you are currently using?
>>>>>>>>>>
>>>>>>>>>> In addition to Sarah and Jerry's comments I would also add  
>>>>>>>>>> that GLX2 stores the script you are working on (hasn't been  
>>>>>>>>>> compiled yet) in the object itself. So the script you are  
>>>>>>>>>> working on follows that object around. So opening the  
>>>>>>>>>> script of the object in another version of Rev running GLX2  
>>>>>>>>>> should still show the script in progress (done this plenty  
>>>>>>>>>> of times myself).
>>>>>>>>>>
>>>>>>>>>> Opening the script in the Rev script editor will NOT show  
>>>>>>>>>> the working script, however, since Rev doesn't know about  
>>>>>>>>>> GLX2 custom properties.
>>>>>>>>>>
>>>>>>>>>> So if you aren't seeing changes as you move between two  
>>>>>>>>>> versions of Rev that are both using GLX2 then my guess is  
>>>>>>>>>> that you have the stack open in both versions at the same  
>>>>>>>>>> time and aren't reloading the stack into memory. If a stack  
>>>>>>>>>> file has been loaded in memory and you change the stack  
>>>>>>>>>> file on disk the changes on disk will not show up in the  
>>>>>>>>>> stack in memory until it is reloaded. Is it possible that  
>>>>>>>>>> this is what is happening on your end?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> -- 
>>>>>>>>>> Trevor DeVore
>>>>>>>>>> Blue Mango Learning Systems
>>>>>>>>>> www.bluemangolearning.com    -    www.screensteps.com
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> use-revolution mailing list
>>>>>>>>>> use-revolution at lists.runrev.com
>>>>>>>>>> Please visit this url to subscribe, unsubscribe and manage  
>>>>>>>>>> your subscription preferences:
>>>>>>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> use-revolution mailing list
>>>>>>>>> use-revolution at lists.runrev.com
>>>>>>>>> Please visit this url to subscribe, unsubscribe and manage  
>>>>>>>>> your subscription preferences:
>>>>>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>>>>>
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> use-revolution mailing list
>>>>>>>> use-revolution at lists.runrev.com
>>>>>>>> Please visit this url to subscribe, unsubscribe and manage  
>>>>>>>> your subscription preferences:
>>>>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> use-revolution mailing list
>>>>>>> use-revolution at lists.runrev.com
>>>>>>> Please visit this url to subscribe, unsubscribe and manage  
>>>>>>> your subscription preferences:
>>>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> use-revolution mailing list
>>>>>> use-revolution at lists.runrev.com
>>>>>> Please visit this url to subscribe, unsubscribe and manage your  
>>>>>> subscription preferences:
>>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>
>>>>> _______________________________________________
>>>>> use-revolution mailing list
>>>>> use-revolution at lists.runrev.com
>>>>> Please visit this url to subscribe, unsubscribe and manage your  
>>>>> subscription preferences:
>>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>>>
>>>>>
>>>> _______________________________________________
>>>> use-revolution mailing list
>>>> use-revolution at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your  
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your  
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your  
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the Use-livecode mailing list