You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by ragb on 2012-02-23 14:26
Currently api.getStatusbar() tries to retrieve the statusbar object from the botom left corner of the foreground window. In some windows such as WiNdows Live messenger the statusbar is not dectected. In the case of windows messenger the statusbar has no statusbar role either but can be customized in the appModule as it is the history Window.
The idea is to provide some method on the appModule class to get the statusbar object. If the module does not implement that method, or returns, None (or some other way to report that it can't find the status bar) the current logic is used.
Is this suitable for inclusion? If yes, shall I write a patch?
The text was updated successfully, but these errors were encountered:
…9792)
Add at AppModule level:
- _get_statusBar : For use by api.getStatusBar to retrieve a custom object
- _get_statusBarTextInfo : For use by GlobalCommands.script_reportStatusLine when resorting to flat review.
Fixes#2125Fixes#4640
Reported by ragb on 2012-02-23 14:26
Currently api.getStatusbar() tries to retrieve the statusbar object from the botom left corner of the foreground window. In some windows such as WiNdows Live messenger the statusbar is not dectected. In the case of windows messenger the statusbar has no statusbar role either but can be customized in the appModule as it is the history Window.
The idea is to provide some method on the appModule class to get the statusbar object. If the module does not implement that method, or returns, None (or some other way to report that it can't find the status bar) the current logic is used.
Is this suitable for inclusion? If yes, shall I write a patch?
The text was updated successfully, but these errors were encountered: