What do you do then? It has a "browse" button, but what should I be looking for?wjaguar wrote:Preferences->Paths->Default palette
mtpaint 3.49.12- April 2016
- Dingo
- Posts: 1437
- Joined: Tue 11 Dec 2007, 17:48
- Location: somewhere at the end of rainbow...
- Contact:
no way to made this change in sources before compiling? It is hardcoded? and change the default canvas from black to white? Sorry for disturbing with these question, for the rest Mtpaint is for me the most powerful swiss-knife for graphical tasks with its command-line counterpart libmtpixel that seems very worthy to be developed furtherlywjaguar wrote:Preferences->Paths->Default paletteDingo wrote:but it would be very useful if there is any way to change the default color in palette when mtpaint starts (red) to white
replace .co.cc with .info to get access to stuff I posted in forum
dropbox 2GB free
OpenOffice for Puppy Linux
dropbox 2GB free
OpenOffice for Puppy Linux
What for, if it can be configured in inifile?Dingo wrote:no way to made this change in sources before compiling?
You can use the global inifile for the purpose, if the user-specific one is, for some reason, not good enough.
http://mtpaint.sourceforge.net/handbook ... html#SEC64
Yes, in a rather unwieldy form (mem_pal_def[] array in memory.c)It is hardcoded?
This line in src/channels.c:and change the default canvas from black to white?
unsigned char channel_fill[NUM_CHANNELS] = {0, 255, 0, 0};
Change the first 0 to 255.
But then, for indexed images, you'll need a palette with color 255 being white - in mtPaint's default one, it is black instead.
With the code as it was, it was a dead-end project - too hard to maintain the GUI branch and the commandline branch in synch, and too extensive differences to merge them into one.its command-line counterpart libmtpixel that seems very worthy to be developed furtherly
With the V-code, there will be hope of combining the two UIs in one program, but the entire GUI needs be switched to V-code first.
And mtPaint could have crashed if you tried that.don570 wrote:However I didn't try to edit the colors.
It was reading a flag value from uninitialized pointer. Fixed in 3.44.34
P.S.: As it happened, part of bug got missed, so 3.44.34 is instead broken utterly and completely. The attached patch fixes it.
- Attachments
-
- mtpaint34434.patch.gz
- (325 Bytes) Downloaded 852 times
New version 3.44.34
Fixes the problem with editing color palette!!
I used patch after decompressing and doing a --dry-run
Fixes the problem with editing color palette!!
I used patch after decompressing and doing a --dry-run
Code: Select all
patch --input=/mnt/sdc1/mtpaint34434.patch --directory=/root/mtPaint-master/src
Do not badmouth my invention!!! If I'd coded it like Microsofties do, mtPaint would already be larger than LibreOffice!don570 wrote:VCODE,
which I believe is code that Microsoft donated to the Linux movement???
It is "V-code" - because it is made of void pointers, like bytecode is of bytes.
The reason for it, is to separate the UI logic from the specifics of GUI toolkit. A V-code chunk describes the composition of a dialog in generic terms, and V-code interpreter then talks to GTK+ on its behalf, to draw widgets, control them, and read back the user input.
And independent of that, V-code is more concise in describing and controlling a GUI - each dialog rewritten in it makes mtPaint binary smaller.
When I tried to compile in Fatdog linux (a 64bit linux distro available
here on this forum) the compiler gave me pointer errors. I was compiling
in fatdog.
The size was wrong ???? according to compiler.
Maybe compiler was referring to 32bits versus 64 bits.
_________________________________________________
here on this forum) the compiler gave me pointer errors. I was compiling
in fatdog.
The size was wrong ???? according to compiler.
Maybe compiler was referring to 32bits versus 64 bits.
_________________________________________________
Since I lack the power of clairvoyance, I need the compiler's error message, exactly as it was, and not a vague description of what it maybe seemed like.don570 wrote:the compiler gave me pointer errors. I was compiling
in fatdog.
The size was wrong ???? according to compiler.
Maybe compiler was referring to 32bits versus 64 bits.
Something could certainly go wrong with all the pointer manipulations that V-code does. But I can neither find nor fix that, if not given any specifics.
Edit: both new and old versions of mtpaint support free rotate.
What is confusing is the menu that it is under. It is NOT under
'Selection' because it does not effect a selection. It is
under 'Image'
Unfortuately mtpaint rotates the entire document,
however mtpaint acts just on one layer. This has
the benefit of using less RAM but also some effects are
possible as well. For instance use the clipboard to place a
portion of your image in a layer above. (You can
save individual layers)
Now do the effect, like rotation, on the top layer.
Use the clipboard to tranfer a portion down to the original layer.
Delete the top layer if you wish.
__________________________________________________
What is confusing is the menu that it is under. It is NOT under
'Selection' because it does not effect a selection. It is
under 'Image'
Unfortuately mtpaint rotates the entire document,
however mtpaint acts just on one layer. This has
the benefit of using less RAM but also some effects are
possible as well. For instance use the clipboard to place a
portion of your image in a layer above. (You can
save individual layers)
Now do the effect, like rotation, on the top layer.
Use the clipboard to tranfer a portion down to the original layer.
Delete the top layer if you wish.
__________________________________________________
Last edited by don570 on Thu 12 Dec 2013, 15:42, edited 1 time in total.
I made a tutorial on how to make graph paper
http://www.murga-linux.com/puppy/viewtopic.php?t=90727
______________________________
http://www.murga-linux.com/puppy/viewtopic.php?t=90727
______________________________
Tested compiling in there. Next time, please do differentiate warnings from errors.don570 wrote:When I tried to compile in Fatdog linux (a 64bit linux distro available here on this forum) the compiler gave me pointer errors.
Anyway, the next version will have that group of warnings disabled - for mtPaint code, they do not communicate anything of value.