The point is that the logger only shows whats really important to know. If you filter it, this may lead to unwanted behaviour that you cannot understand unless disabling the filter again. And this may not come to your mind easily in the case of errors. For example: If you have setup a logging file and this cannot be opened or you run out of disk space, this is reported by the logger. If you filter this, you do not get this information at all. I am unsure what to do here... You sacrifice transparent...
The point is that the logger only shows whats really important to know. If you filter it, this may lead to unwanted behaviour that you cannot understand unless disabling the filter again. And this may not come to you mind easily in the case of errors. For example: If you have setup a logging file and this cannot be opened or you run out of disk space, this is reported by the logger. If you filter this, you do not get this information at all. I am unsure what to do here... You sacrifice transparent...
'About' window can partially open outside of current screen dimensions
'About' window can partially open outside of current screen dimensions
Addressed in [r2096] by introducing a new frame-based custom about dialog
* fix FR#308: 'About' window can partially open outside of current screen dimensions
* updated compiler settings for static linking on ARM
- interim-fix for compiler issue with wxsqlite examples