Bug 421892

+++ This bug was initially created as a clone of Bug #421055 +++
Yet another window rules kcm redesign bug...

Setting a position rule to >4098 (at least X coordinate) is impossible via the new GUI. =:^(

Scenario:

* Dual 4K TVs as monitors in side-by-side orientation, giving me a framebuffer width of 3840*2=7680.

* Most of my main work windows are standardized to 1280x1080, thus allowing me to fit a grid of 3x6 windows on my main work monitor, which happens to be the one to the right (with the one on the left often playing a full-screen video).

* That means the right-most grid slot's X coordinate is 6400 (for a 1280-width range of 6400-7679).

* I like to keep a ksysguard window (RIP superkaramba, unfortunately) in the top-left grid-slot, and I have a window rule to force that position, 6400,0.

* I just had occasion to edit that ksysguard window ruleset for some other reason, and found kwin forcing it to X=4098 after that.  Opening the ruleset I found that the position had been changed to 4098,0, and that while I could reduce that number I couldn't increase it back to the 6400 it should be -- the GUI refused to let me set anything above 4098, either with the spinner or typing it in, or rather, I could type it in, but the window was moved to 4098 and that's what was saved in kwinrulesrc upon upon hitting apply, despite the thing saying 6400 as I actually hit that apply!

* Manually textediting the kwinrulesrc file and running a kwin_x11 --replace allowed me to reset the 6400 position that was supposed to be there, but opening up that ruleset in the kcm to check it, it wanted to reset 4098 again.

Obviously a 4098 cap on position value simply isn't sufficient, especially with 8K displays out (if still prohibitively expensive but hopefully they'll be more reasonable in a couple years) and the possibility of someone running multiple of /those/.  I'd say 16K minimum, if not maxint.