Zagna
-
Posts
509 -
Joined
-
Last visited
-
Days Won
2
Posts posted by Zagna
-
-
In the magic wand image, Ctrl+Alt+Shift+C to copy the selection shape to the clipboard. On the color image, Ctrl+Alt+Shift+V to paste the selection shape.
Move the selection if needed, Ctrl+C to copy a piece of the color in that shape and Ctrl+V on the pencil image. That's one way?
-
Plugins can only access a single layer so comparison between two layers can't be done.
Alternative could be, merge the layers, select the black area with magic wand, Ctrl+Alt+Shift+C to copy the selection to the clipboard.
Undo the layer merge and then Ctrl+Alt+Shift+V to paste the selection back and you can use it on the 2 layers to delete everything that was black on the merged layer.
-
Try changing the setting between font size selection and B.
-
1
-
-
Installer license text is now back to Paint.NET instead of paint.net?
-
8 minutes ago, Rick Brewster said:
From what I recall, there's actually something of a bug in the way PNG -- and I mean the PNG file format itself -- deals with the EXIF metadata for specifying resolution (dpi / dpcm). It can't actually encode certain integers correctly. If you save a PNG at "96.00 DPI" and then reopen it, then the DPI will actually be lower.
I know this because this bug was raised several years ago and I freaked out over it. So I e-mailed with some folks at Microsoft -- because I assumed it was a bug in GDI+ or WIC -- and that's what they told me. It's the PNG file format itself that's broken.
It's the jpg that opens with the wrong resolution. I doodled a 2400x3000@300dpi image, .png saves as it should. Save a .jpg copy of that with paint.net and it opens at 2400x3000@299.
Save a .jpg of the .png with Irfanview and paint.net opens that as 2400x3000@300.
-
1
-
-
Reproduces, using Irfanview to resave it, paint.net opens the .jpg with 300 resolution.
You could use Irfanview to batch process all the original PNG to JPG. Just use paint.net to edit all the .png and then just run a single batch with Irfanview and get .jpg from all of them quickly.
-
1
-
-
12 minutes ago, Reptillian said:
With that update, only XOR didn't get loaded from Krita ora. I could try to add those to the cpp file whenever I get the chance.
Krita is saving it as krita:xor instead of svg:xor since XOR is missing from kis_open_raster_stack_save_visitor.cpp.
-
1 hour ago, Reptillian said:
Here's the name info inside stack.xml in .ora, and it's not they made the patch. I made the patch actually.
I'm thinking…. when saving, save either svg:x or pdn:x.
When loading, if svg:x fails, split the op at the ':' and then try to load it so that for example krita:glow gets split, ('krita','glow'), ignore the first part and try to load pdn:string[1].
And you could add pdn:glow, pdn:negation & pdn:reflect to Krita's kis_open_raster_stack_load_visitor.cpp?
-
2 minutes ago, Reptillian said:
That because it been commited yesterday and can be tested via Krita NEXT - https://phabricator.kde.org/D15584
So, should I export ora using Krita NEXT?
Even in that patch, they haven't added the blend mode import/export to the .ora plugin?
SVG standard lacks filters for Negation/Blend/Glow so I've been using pdn-* definitions.
It all depends when and what names they choose to use for saving the blend mode names.
-
33 minutes ago, Reptillian said:
Is there a way to add a interface for changing blend modes compatibility? Right now, I'm interested in adding a checkmark tool to allow compatibility for Krita. The reason? It is the first notable program to support every PDN blend modes as of today and gmic existence.
I'm looking at Krita's source but I can't find blend modes for Negation, Glow or Reflect? For other blend modes it should support the SVG definitions of them.
-
It seems the path for those files is just that little bit too long, you can try this maybe.
And please, update to paint.net 4.1.5.
-
1
-
-
You can create an anchor next to the <img> inside a <div> that is positioned absolute.
<div style="position: relative;"> <img height="100px" width="100px" /> <a style="position: absolute; top: 30px; left: 20px; height: 20px; width: 20px;" href="#"></a> </div>
Position and size the <a> at the correct position.
-
paint.net 4.1.5 is now available!
- Fixed: The paintdotnet: protocol should now work properly with paths that have spaces in them
That should work? Instead of .exe, just have paintdotnet:%1
-
1
-
No to both questions. paint.net is a raster graphics editor and will stay like that. Inkscape is an excellent vector editor.
-
1
-
-
Looking at the formula, for paint.net that image uses (32073x41147x4)x(3) = 15.9GB of memory.
In addition to that, paint.net starts breaking down with images that are bigger than 30k pixels wide/high.
It's just too big.
-
Just snap the windows to somewhere on the edge of the main window.
-
1
-
2
-
-
1 hour ago, Rick Brewster said:
And what was your solution?
Based on the recent like.
-
On 11/26/2018 at 9:54 AM, X-BIRT said:
(save for a few I got in .ora, but won't be able to use currently).
This might work. Once you update Win 10 and manage to install paint.net.
-
-
This might help find out what's going here.
-
Try turning "Fluid mouse input" off? Let's try that first.
-
1
-
-
Tiny note, updater showed "4.1.3" as an update for this, exe being 4.1.4 and it took 30+ seconds on the 'removing previous version' step of updating.
Installed fine in the end, just something weird. Normally that step is like 1-2 seconds.
-
On 10/27/2018 at 6:14 PM, Alex21 said:
Hi. It will be great to have possibility to bind Paint.NET on PrtScr button. It'll be very convenient for making desktop snapshots. Push PrtScr button, Paint.NET opens and snapshot opens in it. Thanks.
PicPick can do it,
Just press PrtScn and boom, desktop opens in paint.net.
-
2
-
-
To quote the string that was added just recently
QuoteCrashLogDialog.MayBeCausedBy.DieboldWarsaw
Whatever program Diebold Warsaw is, seems to be the culprit.
Paint.net documentation updated for 4.1.6
in Paint.NET Discussion and Questions
Posted
ShapesToolIcon.16.192.png has been shrunk to 32x32 like all the other tool icons when it shouldn't be in 1:1.