Not always about new features - John Jason Fallows

I love a good feature just as much as the next person but sometimes it’s great to fix a small workflow issue that has bugged you for the longest time.

If you have ever seen this kind of dialog you will know what I mean

The good old Python error dialog in QGIS. The dialog is there to tell you that an exception was raised in Python somewhere and would dump out the error for you to debug it. One big issue with this dialog though. It’s blocking. Blocking dialogs are really bad. As a user, the blocking dialog means a broken workflow. Worst of all, there really is nothing you can do about it because the only thing you can do is close.

This dialog has now been replaced with a message bar if something goes wrong in Python code. The message bar is non blocking and lets you continue working even if something didn’t work correctly.

The message bar has two buttons. One will open the stack trace dialog to see the error in more detail. The other button opens the log window.

The message bar will only show a single error message for each type of error even if there are multiple exceptions in a row. A good example of this is an error in a mouse move event handler causing a error on each mouse move.

from Planet GS via John Jason Fallows on Inoreader http://ift.tt/1WAC1Uo
Nathan