Config.xml didn't store many information

[GoogleCodeExporter]

What steps will reproduce the problem?
- Open Image Resizer as usual

What is the expected output? What do you see instead?
- If opening image resizer, the user should re-arange window position, 
re-maximize the window, re-choose the filter method, re-choose border pixel 
handling, etc.

What version of the product are you using? On what operating system?
- R33, Windows 7 32-bit

Please provide any additional information below.
- I think config.xml can be optimized by storing some user setting so they 
didn't need to do some repeating task every time opening Image Resizer.

Original issue reported on code.google.com by ryanb...@gmail.com on 29 Mar 2013 at 2:22

[GoogleCodeExporter]

I will not store window position, nor size because sadly under Windows when 
using multiple monitors which are sometimes connected and sometimes not, this 
can led to an application that starts out of visible range, which is really 
bad. I get this behaviour quite often with other software because I'm using 
such a multi-monitor-setup.

But I could store the last used filter and its settings if this is what you 
want.

Original comment by Hawk...@gmx.de on 29 Mar 2013 at 9:04

• Added labels: Component-Persistence, Type-Enhancement
• Removed labels: Type-Defect