Which is how it 'should' be (but perhaps easier said than done).
One person, half an year: most part of designing, implementing, and transitioning to V-code (while redesigning it on the fly). One person, one month: adding a GTK+3 backend to V-code, with all the investigating and working around the ...

I understand about moving to GTK3.
Once more, proof that ignorance is bliss. :)
Any such move, if started now, is destined to still be in progress, or in a sorry alpha stage, just as the upstream makes the happy jump to GTK4 and breaks everything every which way yet again .
If you believe that the ...

I've often distributed puplets to people and mtpaint is well known for not having the same comfort as drawing tools found in ubuntu or mint distributions for instance
This sentiment, I know. People like what they like (mostly whatever they encountered first, it seems) and there is no changing it ...

BarryK wrote:Yay, 2.2.14 is out! See blog post:
https://bkhome.org/news/202003/easyos-v ... eased.html

And still the included mtpaint is 3.49.12 from year A.D. 2016. Is there a reason for not upgrading?

lvds wrote:we found gnumeric, abiword, mtpaint useless. They may be lighter than LibreOffice and gimp, but they are buggy and useless.

If you found a bug in mtPaint, feel free to name it. If you did not, please stop lying.

I understand that, at least viewnior, uses gtk.pixbuf.loaders. And in my understanding, /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-pnm.so supports "image/x-portable-anymap" and "image/x-portable-pixmap". And, i repeat, neither rox's preview nor viewnior can access these .ppm files (see ...

I've updated mtpaint on my Slackos to 3.44.73 due to translation issues with the delivered versions...
The "issues" being what exactly?
When i edit a scanned .pnm-file in mtpaint and save it, neither viewnior nor gpicview or rox's thumbnail are able to display this file.
I can still open/edit the ...

That is why I posted the bug in the blender forum.
On observing the discussion "when a bug is a bug" there, maybe quoting me there in full was fitting. :) Even if one in three devs has proven himself capable of reading docs on his own.
After your scaring me with the dreaded "bug in mtpaint" phrase ...

I came across a very rare and obscure bug in mtpaint.
Wrong. The bug is in blender.
Image format specs, when we lucked to have them, are meant to be read. Test suites, when we have such, are meant to be used. Image loaders written by left hind appendage without engaging the brain, are meant to be ...

This is a Puppy forum. PeasyGlue is a standard component of Puppy.
Once someone has downloaded the pre-made square.png, they don't need to screw around with mtpaint.
Do I really need to remind Your Obstinacy that mtPaint is a standard component of Puppy too? ;)
They can build any sized grid with ...

Did the PeasyGlue method not work for you?
Given that I myself run Slackware, the answer is obvious.
Which is precisely why the most useful method to solve a problem, is the one that minimizes the number of obscure tools required. Irregardless of any sentimental value the tools in question hold ...

On the gimp I use, the import allows you to change the resolution to 254 which seems to comes out even.
As it should in that case. :) Still, real physical devices with DPI like that, or any multiple of that, are really rare.
The copy of "gv" on Puppy 528 produces a blank page. That looks like a ...

gimp had the same problem as I saw in the window 10 GIMP.
Which is inevitable, as explained above. Pixel grid is not metric.
Document viewer 2.32 had the strange problem of two thick black lines (see image)
The thicker lines should be there every centimeter (i.e. after every 4 thinner ones). But ...

Namely a column isn't wide enough. (see image)
The right column is slightly narrower than left column.
Some rows & columns will inevitably differ by one pixel from the rest. For the simple reason that DPI means dots per inch . No real-life DPI value gives you a whole number of pixels per ...

To cap over the original poster's tantrum, here is a Postscript file for printing graph paper, if anyone would need such: lpr graph.ps
As it is, the file creates an A4 page with margins of 1 cm, a grid of cells 2x2 mm, with thicker grid 1x1 cm. To modify those parameters, open the file in a text ...

I want to create graph paper with squares of 0.2 / 1.0 cm on an A4 sheet, but I can't figure out what numbers to enter into the parameter boxes to obtain this output.
The attached Postscript file should produce the paper you want. Just unpack it ( gunzip ) and send it to printer: lpr graph.ps

If ...

2. In mtPaint: Image->Resize Canvas->Tile
Are you suggesting that the mtPaint method is easier?
It's designed to be that. :) And in addition, this way one does not need a separate program (PeasyGlue) to replicate the original square drawn in mtPaint.
But, as for the really easier method, it would ...

2. In mtPaint: Image->Resize Canvas->Tile

Hi radky! :D
Looks like there are some confusions between /usr/include/ and /usr/local/include/ (??? :shock: ) directories while compiling.

Looks like GLib's pkg-config file does not match install location.
The things just like one you observed could happen if GLib were compiled without passing ...

So whats the latest that runs on slacko5.7 without downloading other files, tweaks, libs, etc.?
Technically, any mtPaint version should build OK on anything more recent than year 2008, given that one of my test systems is still Slackware 12.1. :)
And if it fails to build somewhere, report it as a ...