>>Another example of this is the assertions. You'd get a lot more
>>information if you'd make it possible to report them directly.
>
> Failed assertions generally happen it builn apps, not the IDE so the IDE
> doesn't have easy access to this information.
And while I realize that the new compiler creates a greater separation between
the app being "run" and the IDE, still you know the app is being run from the
IDE, and therefore could, under these conditions, trap whatever information
would be relevant for sending to RS.
With a compiled application, I'd rather be sent this information as is the case
with an unhandled exception, so that I have a chance of modifying my app. And
it might give me clear case I can send in that will help correct the problem
for RS as well.
(I'm not trying to ignore the difficulties here, but I'd like to think I made a
decent case for the benefit of this sort of thing for all concerned.)
> > (Please don't misunderstand, things are much improved wih the new database,
> > but I think the focus is wrong. I think there's too much human effort
> > involved.)
>
> We'll continue to improve the feedback system and we'll certainly consider
> your suggestions.
Thanks. Keep up the good work.
d.
---
A searchable archive of this list is available at:
<http://dbserver.realsoftware.com/KBDB/search.php>
Unsubscribe:
<mailto:realbasic-betas-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-betas-digest at lists dot realsoftware dot com>
.
|