This task would be much simpler, if RB code would be standard text
files. Since projects are not, stripping down stuff is much harder work.
At least for me.
Am 23.05.2006 um 18:33 schrieb Ronald Vogelaar:
Right. Stripping down a project with tens of thousands of lines of
code.
Code that works flawlessly in RB2005r4... and I'd have to strip it
down,
just to get it working in a newer RB version? I don't think so.
Upgrading is
not THAT compelling to me; especially not when you are greeted with a
totally meaningless error message.
Ronald Vogelaar
--
http://www.rovosoft.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adam
Ernst
Sent: Tuesday, May 23, 2006 6:22 PM
To: REALbasic NUG
Subject: Re: Really annoying R2
On May 23, 2006, at 10:43 AM, Ronald Vogelaar wrote:
You don't get it. There is no bug to report. Unless I'd submit the
source
code of my project there's nothing I can do about it. A bug report
should
typically contain a way to reproduce the error. The only thing I
can report
is what I wrote in the previous message.
Wrong. You should strip down your project until the error doesn't
occur anymore, then note what is causing the problem.
Unless, of course, you even get a NilObjectException when running an
empty project, which I seriously doubt.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
