WhoDo wrote:That would require adding exiv from PETget in Puppy-4.2 as this was removed for space considerations.
If user wants Exif handling, he can be expected to install the means of such handling.
Anyway, even if I'd added Exif support to mtPaint, it would still require the library implementing it - most likely, libexif (160 Kb). And adding it won't be a minor change either, for I would first have to devise the means for attaching generic data to undo frames, without wasting a lot of memory on it (given that there can be up to 100000 undo frames).
Dmitry, is there any way to turn off the settings toolbar for first boot? It obscures the pulldown menu and doesn't help the program to look user-friendly.
Given that in Puppy, user's home directory is always /root , you can just place an initial configfile ('.mtpaint') in there, with any changes to the default configuration you want. For the next feature release, I intend to add support for a systemwide "default configfile", but that still needs implementing.
But won't hiding the settings toolbar be counterproductive? People who do not read the manual (i.e., almost everyone) would then not even know where all the controls for drawing modes are.