LiveCode Forums.

Hi all,

Sorry if this is posted in the wrong place. Anyway, First off, I love the enhancements offered by GLX to my Revolution programming environment. However, when GLX is activated, I have to save each script separately by compiling, then saving. With GLX turned off, I just have to save and all is well. I wouldn't be so upset except I lost close to 50 hours of programming because I thought my work was being saved. It gives me the saving icon and all looks kosher. It's only upon reopening that I find
out that I'm screwed. I didn't discover this because I was finishing
scripts within working sessions and starting new ones with a new work
session. I haven't gone back to Revolution in over 2 weeks because I'm
so displeased. Do you have any recommendations for how to fix this error
(maybe something to do with the Win32 engine?). Otherwise, I have to
work without GLX which I don't want to do. So, in a nutshell. Revolution works fine when GLX 2 is turned off. If on, saving only works if I compile and save within each script (which is very tedious, especially when you're moving code from one script to another and have to compile and save each script separately).

Have you contacted the developers directly?

http://daniels-mara.com/

The default save settings were prevented my work from being saved. Now all is well. I still lost a lot, but the archive system will make up for it over time.

Josh, GLX2 does a fine job of saving your work as you go along using the auto-saving and auto-archiving settings, provided you do two pretty much common sense things:

• Go to preferences
  Check Auto-save and/or auto-archive

NOTE: You DO have to save your stack manually at some point so that there is a file on your system that GLX2 can save to. If you don't save your stack to file at SOME point, the auto-save, etc. has no place to save.

Jerry, is it me or is there testiness in your response (the "does a fine job" and "common sense" comments, in particular). If it's just the impersonal nature of text and I'm misreading your post, never mind. However, if you are being rubbed the wrong way by my post, then there are better ways to handle it than posting a testy response. It would have been common sense for the preferences to be set up to auto save and auto archive by default. Mine wasn't for whatever reason. I lost a lot of work which I accept, but I praise you for your product. Now that the options are set up correctly, it's a marvelous product that I will continue to use for years to come.

Josh wrote:It would have been common sense for the preferences to be set up to auto save and auto archive by default.

I don't use GLX2 so I can't comment on its functionality specifically, but in general I'm not sure that auto-save should be on by default in most apps that provide such an option.

One of the commercial apps I produce has an auto-save feature, and we shipped with it turned off by default. We did this because most apps leave the user in control of when they choose to save, and in general I agree with those designers that leaving the user in control whenever possible is usually a good thing.

In your case, while changing the auto-save behavior appears as though it would have been useful, if I understand your description of the problem correctly it's not so much about auto-saving as simply the manual saving not working as expected. If it had, auto-saving would not have been as critical.

Josh, no...not rubbed the wrong way at all. Was in a hurry, tho. Working away here. Hope my comments were helpful, however. I don't believe in emoticons, so some of my thoughts can be misread. It's usually more obvious when i get "testy" or even "testee". (Couldn't resist.)

So it appears that "GLX Causes Serious Problem" may not be an accurate headline. Did it cause the problem? Or did it work as documented and advertised? Should auto-save be turned on by default? Is this a flaw? I agree with Richard that it should not be the default as Rev does not save by default.

But given the current climate that newspapers and technical writing, I really can't fault anyone for exaggerated or premature headlines. Truth is, my own promotion of GLX2 is hyperbolic. It's just a script editor. It can't stop inflation, for example.

Josh, have some fun with GLX2 and create some great stuff! Thanks for using it, too!

Hi Josh,

First off I would like to thank you for your purchase of GLX2 from our company, it makes both Jerry and I very happy, and I am also glad to hear that you will continue using our product for years to come (gives me a warm fuzzy feeling). I know the auto save thing can be frustrating, but please remember we are an add on, we don't actually change the way rev saves files. If the stack has never been saved to file auto save does not do anything at all (Just FYI).

Secondly, I know the Runrev holiday bundle had alot of products in it, and it all was sold through Runrev, but usually the only place we do product support is on our support site. In fact, the exact problem you had has been not only been posted, but also had the solution to the problem posted as well for some months now. On the site we do answer questions as quickly as possible, and as you can see have a knowledge database to answer common problems.

Are you signed up for support yet? If not shoot me an email at joe@daniels-mara.com and I will sign you and any one else that has a current version of the GLX2 up for the support site. Hopefully being on the support site will not only help you solve problems, but give you a heads up on problems before you have them.

Many Thanks,
Joseph @ Daniels & Mara, Inc.


Hope you continue to enjoy our product.