Demo Show Stopper - Save File Dialog
dan at clearvisiontech.com
Mon Apr 26 13:47:28 CDT 2004
Your absolutely right - without question, RR should fix this issue. I guess
I'm more lenient about small issues like this. I get upset about the big
issues. Several years ago there was a bug in the toolTip property. If you
had a toolTip assigned to ANY object, the standalone would crash when you
issued a quit command on Macintosh systems. This got me to stand up and
shout. Not so much because there was a bug, but because the bug wasn't
documented anywhere. At the time, I was not skilled enough to track down
the problem. I ended up hiring an outside consultant to track down the
problem - which they did. RR fixed the problem in the next release. And,
RR is getting better about fixing problems and it's support policy. Then
again, this list is better than ANY support you'll find anywhere!!!
Let's not forget that no application is 100% bug free. Not WindowsXP, not
OSX, not Word, not Photoshop, not RR, and certainly not my applications!
But, we all continue to do our best and hammer out the bugs.
I have used RR for 3 years now. I know it well enough to know it's
stability. And, I can tell you, in my experience, it's pretty strong. I'll
admit that RR's IDE is a bit quirky. There are some things (like the save
prompt) you just have to let go by [until RR fixes them]. In my case, I'm
not so concerned about RR's IDE as I am my final product. I deploy all my
products as standalones. So, I test as a standalone, not in the IDE. If it
works as a standalone, then I move on to the next thing I can make money
I used to work in C++. The problems I ran into with Metrowerks' IDE and
their libraries (Not to mention C++ builder - Jeez!!) are FAR more
devastating and catastrophic than I have ever seen in RR. And, as an added
bonus, I write way less code, in literally a fraction of the time!
All the best,
> Well it isn't actually "solved" by a single click is it? Really it's
> swept away under the carpet by a "single click". If something as
> simple as this doesn't work relaibly, then what else doesn't work?
> What else has been swept under the carpet?
> It's not so much that this problem exists that is worrying, but
> rather that know one seems to know how to even start to know where to
> look to even try and fix it! And your advice is to ignore it!!!!!
> This is supposed to be a "Professional" software development package
> - I don't think that ignoring a problem like this is in any way
> And you are right, it's not "worth" spending 12 hours on, it's not
> worth spending even 10 minutes on, but if I can't make it work then I
> there will be no confidence in RR as development tool and there will
> be no confidence that there is any support to get problems like this
> Sorry to be sound tetchy but I am, I just cannot beleive that we have
> paid over $400 for something that has basic problems like this in it.
> I mean if you can't save reliably (and then know you have saved) then
> what's the point?
> All the Best
>> I have this very same problem. Here's what I do... When I get the "Do you
>> want to save this Stack?" dialog, I simply click "Save" and move on. It may
>> be a little annoying, but in my opinion, it's not worth spending over 12
>> hours on. Revolution is an amazing product! I certainly hope you don't
>> stop using it over something that can be solved by a single click.
More information about the use-livecode