Quote:
Originally Posted by NiLuJe
@Mavireck: That was kind of the idea behind the dump/restore API  (c.f., @sherman's original FR [and my ramblings ;p]).
At least as a backend for that kind of thing, possibly coupled with print_raw_data for more esoteric use-cases.
I vaguely recall seeing you use the dump/restore API before, so I'm curious as to what led you to stick to print_raw_data for this?
(That's a perfectly valid solution, mind you, just asking in case something can be done to make the dump/restore stuff more approachable/practical ). |
I did use your dump and restore API before. It is working very well, and I had absolutely no issue with it!
I can't see if a way to improve it, it is just that I needed something much more powerful than only dumps and restores
For my dashboard, I needed at some point to update an image which was partially hidden by another one. The problem is, I did not quite have an easy way of knowing how the area they occupy intersected each other. (and it is more and more of an issue if you have a lot of items on screen). Instead of coding it manually for every single situation, I sat for a few hours to make KSSM, which does all that for you
In short, dumping and restoring works great as long as your app remains small, but after that it gets more and more complicated.
If you don't believe me, have a look at the test file, with the 3 rectangles thing.
If you can, try it.
It is extremely easy to use, but I could not think of an easy and general way to do the same thing with dumps and restores
(or at least, not such an easy way)
Also please note that it is still widely WIP, one day ago it was only in my head