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?
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?