midora
-
Posts
1,782 -
Joined
-
Last visited
-
Days Won
26
Posts posted by midora
-
-
Hi Rick, there are several tool plugins which do not expect that a dummy token is needed. There is no ETA because the current rules require to use the latest interfaces and environments. That's just too much work in the moment.
-
As @Ego Eram Reputosaid use Copy/Paste selection for more complex things. You may even Copy Selection, paste it into a basic text editor (its pure text) and save it for later use. Means you can load the selection file to the text editor, copy it to the clipboard and use paste selection in paint.net.
-
Hi @hbgodseekerafter creating the basic ellipse selection you can use the move selection tool to change the size and rotation of the selection. Move the mouse pointer near to the border of the existing selection. At a certain distance a rotation arrow will appear. Grab it and rotate the selection. The angle will be visible in the status bar.
-
1
-
-
I would expect that creating an empty dummy token in 5.0 would also solve the issue. Non-tool plugins would just override this token.
-
Accessibility: Mouse Pointer Size
If paint.net could adjust is cursors using the multiplier provided in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Accessibility\CursorSize then this would help some users.
In the moment only the standard arrow and move selection adjusts its size. Size is 16 * (CursorSize + 1). CursorSize [1..15].
BTW: I'm getting the system move cursor for Move Selection and Move Selected Pixels. I thought that earlier they looked more like the icons in the tool window but it's the same in 4.2.16 (win 10) so maybe I'm wrong. -
19 hours ago, Rick Brewster said:
- Fixed many long-standing issues with keyboard/mouse focus, whereby tool shortcuts would not work when the mouse was in certain places (e.g. over the Tools or History window)
I did various tests and for me this fix worked flawless on Win10 now.
What I'm still missing is a solution for the non-letter control shortcuts like Ctrl++ (Zoom In) in various keyboard layouts. I expect that paint.net looks for Ctrl+OEMPLUS and Ctrl+ADD. But in many cases you have to add Shift to reach the plus sign. So this is not working in paint.net.
In my own applications I'm asking the system which key code produces the plus sign and add Ctrl to get the right key combination.
if (keyData == DeviceKeyboard.OemCharacterToKeys(Keys.Control, '+')) ...public static Keys OemCharacterToKeys(Keys modifiers, char c)
{
return modifiers | CharactertoKeys(c);
}private static Keys CharactertoKeys(char c)
{
// Map character to scan code
short scanCode = VkKeyScanW(c);// Translate scan code to key
Keys key = (Keys)(scanCode & 0x00FF);
if ((scanCode & 0x0100) != 0) key |= Keys.Shift;
if ((scanCode & 0x0200) != 0) key |= Keys.Control;
if ((scanCode & 0x0400) != 0) key |= Keys.Alt;return key;
}[DllImport("user32.dll", CharSet = CharSet.Unicode)]
private static extern short VkKeyScanW(char ch);This would work also if you are changing the keyboard layout while the application is running.
To center the content below the mouse pointer in the window Ctrl+. may be used (together with shifting the mouse using Cursor.Position=centerPoint).
-
It was just not required to add a token up to now. There was no abstract definition or documentation which forced you to do it. I try to keep sw minimal. I asked about tool plugins which do not modify the image (to avoid the useless call of copying the current content in Render()) i.e. by a configuration flag. Why is this not possible? I had no intention to make you developer life more difficult 😉
These tools have been used for years without any issue. If they now fail in 5.0 then something has changed in the internal handling of plugins and they are no longer compatible. You can spent some time to keep them alive or not and block them. Or discuss a better solution for these kind of plugins. That's on your side.
-
Create the horizontal lines at the top, cut out a triangle (60 degrees). Copy and paste them rotated by 60, 120, ... degrees.
-
45 degree lines. Width 1; 1,5; 2
-
Entering 1, 1.5, or 2 produces different results in 4.3.12 here, drawing a line. Maybe it has just effect to anti-aliasing but it has an effect to how wide a line looks.
-
You may enter a value between 1 and 2 in the text box but I doubt that you can recreate the line perfectly.
-
Why should anyone call ctrl-f on a tool if ctrl-f never opens a dialog? BTW: Because these kind of tools never exit with ok they do not appear in the ctrl-f menu.
-
Without the flag there was no dialog. We talked about tool dialogs which do not need a configuration (and no progress bar). It worked without creating a token.
-
I can only guess that the issue is that the plugin doesn't use an EffectToken. Same happens in WhatIsIt plugin on close.
-
1
-
-
-
Because .agif is handled from a plugin you have to install a shell extension to get a thumbnail of an image in the shell (the explorer).
-
2
-
-
My local version is working (no wonder, me and others need it) but for specific reasons I can not publish it in the moment. I will have a look after .net 7 has been released.
-
1
-
1
-
-
Hi @WaffleKingthere is no way to do this because the paint.net plugin api only allows to access the current layer.
-
Sometimes people are saving an image with the wrong extension. You may use the 'What's It?' Tools Effect Plugin to check and fix it.
-
@dvc4you may use the 'What's It?' Tools Effect Plugin to check the files showing this error or upload one (must be family friendly).
-
1
-
-
Hi @MylarDaleTolo if you know how, you may create a little tutorial...
-
I would check in the registry if the open command contains more than on "%1".
-
1
-
-
You have to copy the files into the FileTypes folder and not into the Effects folder.
-
New release 1.1 (24.3.2022)
- Fixed compatibility issues with paint.net 4.3.10 (which is required now)
- Added some new file formats like AVIF and JPEG XL
- Added a 'Fix' button. Enabled in case the file uses an unexpected extension.-
2
-
1
-
1
-
'What's It?' Tools Effect Plugin [Latest v1.1 2022-03-24]
in Plugins - Publishing ONLY!
Posted
Fair enough. Thanks.