Bug fix on try control giving unwanted warning in the output window

[shadrackkibet]

@lloyddewit this is a fix to avoid a warning message in the output window when debugging. You might have noticed that there is a warning on the compilation as shown in the below screenshot.

Investigations show that this originates from a warning in ucrTry line 217.

[shadrackkibet]

@africanmathsinitiative/developers this is ready for review.

[lloyddewit]

@shadrackkibet I am very happy to see this warning disapear :)
I tested with the calculator dialog:

• entered invalid calculation
• pressed try
• pressed '...' to view details
• pressed ctrl-enter to exit popup

Everything worked correctly

[lloyddewit]

@rdstern please could you test? thanks

[lloyddewit]

@africanmathsinitiative/developers this is ready for review.

no longer needed

[shadrackkibet]

@shadrackkibet I am very happy to see this warning disapear :)
I tested with the calculator dialog:

• entered invalid calculation
• pressed try
• pressed '...' to view details
• pressed ctrl-enter to exit popup

Everything worked correctly

Thanks for testing.

[shadrackkibet]

@rdstern?

[rdstern]

Good

[Patowhiz]

Another related annoying warning is when opening the design view of some dialogs. This is caused by visual studio running commands even in design mode and finding nulls due to absence of connection to R. This could be addressed in another PR. It's more or less 2 lines of code being placed in strayegic places to detect whether the environment is in design mode or running mode.

[lloyddewit]

@shadrackkibet Thanks for adding the bug label and changing the title. I added the skip-release-notes label because I didn't think this fix was relevant for users.

[lloyddewit]

Another related annoying warning is when opening the design view of some dialogs. This is caused by visual studio running commands even in design mode and finding nulls due to absence of connection to R. This could be addressed in another PR. It's more or less 2 lines of code being placed in strayegic places to detect whether the environment is in design mode or running mode.

@Patowhiz Thanks for the suggestion. I rarely work on the dialogs so I don't experience this annoyance. If you think that the fix is simple enough to be worthwhile you could raise an issue.