thehx

very inconvenient input (takes lot of toying with coordinates until the rectangle finally fits into desired trapezoid), but certainly doable. Thanks! Is there an option to just specify the target quad's 4 vertices coordinates assuming the source rect being the entire layer (or select the TL-BR of the source as well)?

How can I achieve the inverse transformation, i.e. translate rectangle to fit into some trapezoid on a photo for example?

Restarting paint.net helped, but this occasionally happens. Maybe it sometimes happens upon resolution changing and/or (dis)connecting additional monitors.

Hi guys, the problem is exactly what the title says. Video of the problem

Ok, I tried the new version of the plugin as toe_head2001 suggested. Works fine, or at least so it seems to me, so far. Thank you!

First of all, thanks for the amazing editor! I know this is not the section for plugin errors, but I believe that the plugin itself is working fine, because I encountered this for the first time only recently, and I definitely remember my Paint.NET updating a week ago or so... The recent update broken the ico/cur plugin, it seems. On opening an ico file, the entire app freezes due to the modal window, that asks the user to pick which icon to open, not showing on top of the Paint.Net window. Some alt-tabbing back and forth helps bringing said modal window back from the abyss... I've been using the ico/cur plugin for years, and the modal window that is used to pick the resolution or open everything in different layers never presented any problems to me until now. In case it helps, I'm using win7pro 64-bit, with a classic theme. I've uploaded a video showing the weird behavior. I should also make clear that this bug is of very strange, fleeting nature. After a few tries with a single instance of Paint.NET, the weird behavior usually disappears, and the modal window shows as it should, but once I restart Paint.NET, I'm getting the freezes (i.e. modal dialogs behind the main window) again. I do not want to spam and duplicate this topic into the plugins forum branch, but if it belongs there more than here, please move it.

First of all, the first scenario is sufficient [for me] to have Paint.NET crashed: Second, yes, by "hide" I meant "uncheck layer visibility", sorry for not being clear enough. I believe the crashes happen due to a race condition occuring when the number of layers is decreasing rapidly... or I just can't make a better guess.

If this can help, below is the extraction from Windows Event Log.

Strangely enough, the logs folder is empty. Here is what exactly the fox says: Signature: Event: APPCRASH Application: PaintDotNet.exe Version: 4.5.5454.39504 Application timestamp: 5484cd44 Error module: MSVCR120.dll Error module version: 12.0.21005.1 Error module timestamp: 524f83ff Exception code: c0000005 Exception offset: 000000000003c3f9 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1049 Additional info 1: ad75 Additional info 2: ad7539a1050cd947e7161d5ea2ce0e0a Additional info 3: 7b38 Additional info 4: 7b38baf94350760d182377a53254f518

Win7-64.pro @ Dell Precision M6800 (16GB RAM, half of which are free when I start Paint.NET to reproduce the issue). Strangely enough, I couldn't find (or, more precisely, couldn't "find | grep pdncrash\.log" in a git bash window) the crash log at all. When paint.net crashed, I only observed the standard Windows message saying "The program is going to terminate, you may try debugging it...". I searched the whole users folder (which is, %appdata%/../..) for it via find|grep, since I don't quite trust the windows search. In case it could be of help, here is the full list of plugins I am using (although Paint.NET crashes even when I do not use any of them): Effects: MakeTransparent.dll (I am using it since Paint.NET 3.0) FileTypes: IcoCur.dll, AnimatedGifLibrary.dll PS. Usually, when a plugin crashes, Paint.NET offers to save whatever I've been working on. In this case, it just dies, no questions asked, leaving me watching all the unsaved changes sailing to the land of eternal spring. PPS. ..or is there an autosave plugin?

To reproduce the bug, 1) create an empty image, 800x600 2) Ctrl+A, Ctrl+C, hold Ctrl+Shift+V for around 10 seconds, then hold Ctrl+Z (in hope of undoing making these additional layers) 3) Fatality! To those who think the scenario above is far too unusual to cause any real trouble, here is the simpliest possible way to shoot yourself in the leg with no intention to do it: 1) Draw a background and hide it 2) Create a drawing on a layer with opacity around 5% and rendering mode other than default 3) Ctrl+Shift+C the nearly-transparent drawing 4) Delete the now-useless drawing layer, display the background layer, then repeatedly hit Ctrl+Shift+V until everything looks as planned 5) Realize that the final result is totally unacceptable (either because it really is, or because of someone else's bleeding eyes) 6) Hit the Ctrl+Z pedal to the floor, to unwind those 10 or 15 new layers 7) All your unsaved work is gone... Attack the wall with own head, I suppose, unless your auto-saving instinct is on a level when you hit Ctrl+S before drawing a line, after drawing it, before zooming out to check how it looks in a big picture, and after zooming back in. PS. The same thing often occurs in similar scenarios involving adding or removing layers too quickly (You may use Ctrl+M, for example)