@gid: Yeah... I suspected it had something to do with that. It was the only absolute change I introduced. Unfortunately, I had to means to test it in other system. 
Thanks for removing that and for providing more fixes for the shaders under AMD. Great job!
@andutrache:
1.-
2.- I decided not to allow saving this in the Settings.properties right in r2006 because I was afraid it could be an unstable feature. Turns out I was right, but for the wrong cause.
Saving the filter status and the selected resolution should be easy to add.
3.- Yes, this is normal. The only resolutions that should not corrupt the graphical display are the native ones 480x272, 960x544 and 1440x816. The others need a more complex rescaling, so they're still a TODO feature.
4.-
5.- Any improvements with dynamic shader generation?
6.- Hmm... Could you send me some screenshots, with any test application running, demonstrating the resizing?
7.- This may be also normal. Full screen still needs more improvements, like the removal of the window's decorations before the full maximization. Unfortunately, Java makes this a quite hard task because it envolves disposing the current window, setting it's undecorated parameter to true and then build the window again. I'm currently looking for better ways to implement a workaround for this.
@Vegerunks: Are you still experiencing low FPS after gid's fixes in r2014?
Thanks for removing that and for providing more fixes for the shaders under AMD. Great job!
@andutrache:
1.-
2.- I decided not to allow saving this in the Settings.properties right in r2006 because I was afraid it could be an unstable feature. Turns out I was right, but for the wrong cause.
Saving the filter status and the selected resolution should be easy to add.
3.- Yes, this is normal. The only resolutions that should not corrupt the graphical display are the native ones 480x272, 960x544 and 1440x816. The others need a more complex rescaling, so they're still a TODO feature.
4.-
5.- Any improvements with dynamic shader generation?
6.- Hmm... Could you send me some screenshots, with any test application running, demonstrating the resizing?
7.- This may be also normal. Full screen still needs more improvements, like the removal of the window's decorations before the full maximization. Unfortunately, Java makes this a quite hard task because it envolves disposing the current window, setting it's undecorated parameter to true and then build the window again. I'm currently looking for better ways to implement a workaround for this.
@Vegerunks: Are you still experiencing low FPS after gid's fixes in r2014?