More specific error reports

The following interfaces have been changed to facilitate better categorization and more information for crash reports now.

cm.recovery.recoveryBits.cm

Old: public void sendBitsBugReport(str subject=null, Url drawing=null, Window parent=null) {
New: public void sendBitsBugReport(ErrorDialogArgs args=null, str subject=null,
			      Url drawing=null, Window parent=null,
			      str stackTrace=null, CallStack callStack=null) {

Old: public void sendFeedbackReport(ErrorDialogArgs errorDialogArgs=null, bool forceCrash=false) {
New: public void sendFeedbackReport(ErrorDialogArgs errorDialogArgs=null) {

For crash reports use sendBitsCrashReport reports instead.

More specific error reports

We have made some updates to the error reporting dialog to have better categorization and more information for crash reports. The following interface now sends reports as bug reports.

cm.recovery.errorDialog.cm

public void addReportErrorButton(FlexDialog d, ErrorDialogArgs errorDialogArgs) {

To send reports as feedback or crash, use the following interfaces instead.

Feedback: public void addReportFeedbackButton(FlexDialog d, ErrorDialogArgs errorDialogArgs) {
Crash: public void addReportCrashButton(FlexDialog d, ErrorDialogArgs errorDialogArgs) {

Also crash reports require a stack trace string or call stack now so that crash locations are now traceable and will trigger a devassert if the stack traces are empty (sendBitsCrashReport or addReportCrashButton).