The first seems simple enough. Just store the x,y onmove, read it onlaunch, check that x,y is valid and move the window accordingly.
The second is even more simple. Just remember the sidebar width. Just wang it in gconf if there isn't a better place. I think this might even be a regression.
To display these bugs just move your window from its launched position, resize the sidebar, exit gwibber and launch it again. Note: I'm not talking about minimising to tray; you have to close it completely.
Gwibber forgets to persist two things:
- Window position
- Sidebar width
The first seems simple enough. Just store the x,y onmove, read it onlaunch, check that x,y is valid and move the window accordingly.
The second is even more simple. Just remember the sidebar width. Just wang it in gconf if there isn't a better place. I think this might even be a regression.
To display these bugs just move your window from its launched position, resize the sidebar, exit gwibber and launch it again. Note: I'm not talking about minimising to tray; you have to close it completely.