mtPaint development

[HairyWill]

When using the polygon selection tool, is there anyway of undoing the last point(or more) selected?

[Lobster]

Trying to do something before the engine changes would amount to nothing but putting lipstick on a pig.

Well personally I wouldn't call mtpaint a pig
We have had this conversation before
http://www.murga-linux.com/puppy/viewto ... 327#147007

Looking forward to the changes you are implementing

[wjaguar]

When using the polygon selection tool, is there anyway of undoing the last point(or more) selected?

Not implemented yet.

[Plume]

I found in this topic how to read exif data using exiv2. That's fine. However, after saving a picture there is no more exif data. Is there a way to save exif data when saving the picture itself?

[MU]

oops, wrong thread, sorry
Mark

[wjaguar]

Is there a way to save exif data when saving the picture itself?

Currently, there isn't.
The reasons are twofold. One, I don't myself do digital photography, so I don't even know why preserving Exif data through image edits is needed at all (and "Just because!" isn't a good answer, because making that happen would be anything but trivial). And another, libjpeg which mtPaint uses to read and write JPEG files knows nothing at all about Exif, so I would need to link to a separate library for Exif handling - and as far as I know, there isn't any one such library accepted as a de facto standard. The most popular ones seem to be libexif and libexiv2 - and still, some distros ship with one, some with another, others with both, and still others with neither.

-= With best regards, Dmitry Groshev, maintainer of mtPaint =-

[Plume]

Thank's for your answer.
The most important information I would like to save is the date/time the photo was done.

[wjaguar]

The most important information I would like to save is the date/time the photo was done.

One possible workaround could be to extract Exif data from the file before edit ('exiv2 ex filename.jpg'), and put them back afterwards ('exiv2 in filename.jpg'), provided the filename stays the same.

[WhoDo]

The most important information I would like to save is the date/time the photo was done.

One possible workaround could be to extract Exif data from the file before edit ('exiv2 ex filename.jpg'), and put them back afterwards ('exiv2 in filename.jpg'), provided the filename stays the same.

That would require adding exiv from PETget in Puppy-4.2 as this was removed for space considerations.

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.

Thanks

[wjaguar]

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.

[WhoDo]

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.

Got it, thanks.

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.

You mean like we had in 3.21 for Puppy 4.1.2? Maybe forcing them to read the manual to find out is a good thing? I just found that the two windows on boot was confusing, especially since its position obscured the main menu. I just didn't know what I was supposed to do with the settings menu when it popped up. Maybe I'm just not a heavy-enough user for that.

[Flash]

There is no "Help" heading along the top of mtPaint, nor can I find mtPaint in Puppy's Help menu which links to online documentation for Puppy's included applications. How are the many Puppy users who are new to Linux and the open-source community supposed to know there is a manual for mtPaint, never mind where it is?

[WhoDo]

There is no "Help" heading along the top of mtPaint, nor can I find mtPaint in Puppy's Help menu which links to online documentation for Puppy's included applications. How are the many Puppy users who are new to Linux and the open-source community supposed to know there is a manual for mtPaint, never mind where it is?

There is on my mtPaint, Flash! It's at the far right on the drop down menu bar. The "Documentation" heading gives instructions on how to install Help (since we don't include it by default), and the "About" heading gives shortcut key codes, etc.

[wjaguar]

I just found that the two windows on boot was confusing, especially since its position obscured the main menu.

The position is stored in the same configfile, so you can just move the settings toolbar out of the way, and make that the default.
And yes, I see your point - the default position of settings toolbar really could be chosen better. It is just that I don't myself get a chance to see it in default position often.

BTW, why not put a link to http://mtpaint.sourceforge.net/handbook ... ap_00.html into Puppy's Help menu? Lately, I see a bit too many people who don't even know mtPaint is supposed to have a manual - so it would be useful to make the manual easier to find.

And one more thing - when is Puppy 4.2 expected to be released? I have several bugfixes for mtPaint 3.30, and am going to do the 3.31 bugfix release soon - and it'd be unfortunate if I released it too late.

[Flash]

There is no "Help" heading along the top of mtPaint, nor can I find mtPaint in Puppy's Help menu which links to online documentation for Puppy's included applications. How are the many Puppy users who are new to Linux and the open-source community supposed to know there is a manual for mtPaint, never mind where it is?

There is on my mtPaint, Flash! It's at the far right on the drop down menu bar. The "Documentation" heading gives instructions on how to install Help (since we don't include it by default), and the "About" heading gives shortcut key codes, etc.

Oops I never look in the corner, away from the rest of the headings. Here's what I get when I click on Documentation:

[`f00]

one - procure here, save ..
or a more recent version and extract ..

two


three


four (optional) - try Help again
this time, it's LOCAL - look Ma, no internets needed!

[WhoDo]

BTW, why not put a link to http://mtpaint.sourceforge.net/handbook ... ap_00.html into Puppy's Help menu? Lately, I see a bit too many people who don't even know mtPaint is supposed to have a manual - so it would be useful to make the manual easier to find.

Agreed.

And one more thing - when is Puppy 4.2 expected to be released? I have several bugfixes for mtPaint 3.30, and am going to do the 3.31 bugfix release soon - and it'd be unfortunate if I released it too late.

Assuming the last few items of cleanup go as planned, I'll probably release 4.2 Final around Wednesday of this week (my time GMT +10). If you need any more time just let me know. I'd be happy to hold off for the right incentive!

[wjaguar]

Assuming the last few items of cleanup go as planned, I'll probably release 4.2 Final around Wednesday of this week (my time GMT +10). If you need any more time just let me know. I'd be happy to hold off for the right incentive!

Myself, I plan to release version 3.31 the next weekend (i.e., on March 28th or 29th) - but as far as bugfixes go, version 3.30.03 here already has them all. What isn't yet done is updating docs (the handbook released with version 3.30 had a few things left out) and adding a new small feature or two (I don't like to do pure bugfix releases).
So if you would rather release Puppy 4.2 before March 30th, you can just use the version 3.30.03 without missing anything important - but waiting till proper 3.31 release is going to be at least somewhat rewarded.

[synth]

@wjaguar: mtPaint has a serious (usability) issue: Resizing a selection vertically or horizontally is a pain in the butt.

Try this little freeware app for Windows (works with WINE):

http://photofiltre.free.fr/utils/pf-setup-en.exe

and see how the horizontal / vertical resizing works there. Then you'll see what's wrong with mtPaint.

[wjaguar]

@wjaguar: mtPaint has a serious (usability) issue: Resizing a selection vertically or horizontally is a pain in the butt.

mtPaint does not implement the very concept of "selections" - so, quite obviously, cannot do any operations on them. There are images which get modified, and clipboards which get copied and pasted - with nothing in between.

Try this little freeware app for Windows (works with WINE):
http://photofiltre.free.fr/utils/pf-setup-en.exe
and see how the horizontal / vertical resizing works there. Then you'll see what's wrong with mtPaint.

If you think there is an usability issue with mtPaint, then present an use case - with a clear example and at least a bit of explanation. I don't have time to waste hunting for obscure hints in Windows programs I never before used - and puzzle-solving never was my favorite occupation.

And if you like Photofiltre, then you might want to do something to help with its Linux port: http://pflx.x10hosting.com/.