![](http://content.invisioncic.com/r125076/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
Gambo
-
Posts
11 -
Joined
-
Last visited
Posts posted by Gambo
-
-
That would save some clicks for those who use the same script every day and would definitely be great!
-
Settings will persist throughout a Paint.NET session, but will be forgotten once Paint.NET is closed. The same applies for all plugins. If you need persistence, you can create a ScriptLab script that runs Borders N' Shapes with the desired settings, and use that script to add your borders.
Thanks for the hint. ScriptLab looks very promising. This brings up a follow-up-question: can I make ScriptLab remember/initially load a certain script so I don't have to click Load and search and select/open the scriptfile in each new PDN session?
Edit: Ok, I think I get it. Since ScriptLab is also a plugin anything you said applies to ScriptLab as well, so this isn't possible, right?
-
This thread seems quite old though Borders N' Shapes is actually no more v1.6 but 1.7 but I couldn't find another thread about it.
Just one thing: love that plugin and use it to -guess what- but borders around images, but in a repeating certain color and width. Sadly, the settings won't stick between sessions; it always starts with a 2px black border.
Is there a way to make my personal settings persistent (either by me or by you :wink: )?
-
When I select something on the workspace and press M I'm in the "Move Selection" mode where I get 8 handles to resize and move the selection.
It confuses me each time that when I place the cursor in the middle of the selection to move it I get a resize-cursor (arrow) and when I grab a handle I get a move cursor (hand):
I think those should be swapped to make working with selections more intuitive.
-
The built-in updater downloaded the program. But as this install failed I downloaded separately again from http://www.dotpdn.com/files/Paint.NET.3.30.zip
I had Paint.NET on this PC for a long time and updated regularly without any problems.
-
Sorry, I didn't meant to say it was Paint.NET's fault, I was just glad having tracked it down.
But you got me wrong: the problem was not the ZIP, it was the EXE inside that actually IS a self-extracting ZIP itself (so this is double-zipped).
-
I uninstalled the .net frameworks 2 and up and reinstalled 2 and 3. Nothing.
Than I tried to read what flashes on the window that quickly closes after opening. It said "Extracting..." which made me try an idea:
I tried to open the file "Paint.NET.3.30.exe" in 7-zip and found a "PaintDotNetSetup.exe" and some other files.
When I started the "PaintDotNetSetup.exe" manually Paint.NET installed without problems.
Problem solved, so the flaw was somewhere in the extracion routine.
Anyway: I'd recommend to offer not only a ZIP download that contains an EXE that again contains some other files.
Better would be to offer two files:
• an EXE (that one that's now in the ZIP) for the normal user
• a ZIP with the real installation files (those that are now in the EXE) for advanced users
-
Ok, I'll try repairing. One thing: I seem to have the .NET Frameworks 3.5, 2.0 and 1.1 installed; does the order of reparing matter?
-
Yes, I tried restarting; that didn't help. Still no way to install v3.30.
Regarding the 1023 MB: I have no idea. The graphic card is a nVidia GeForce 7600GT with 256MB own memory
-
Hi,
I have two equal PC where paint.net is installed and running since a long time (also with the same plugins).
Today I was trying to update from v3.22 to v3.30. I used the buildt-in update functionality.
1st PC: no problem, the update went fine.
2nd PC: the update file loaded, the installation started. I received the known message that Paint.NET has to close down to continue. After that I received an error message (I remember something with "...due to an unknown error...") and the installation stopped.
This was reproducable so I uninstalled v3.22 to have a clean machine. Then I tried to install v3.30. The installation starts with a window that appears for about 1 second. Then the window disappears and the installation stops.
So I'm stuck and can't install v3.30. Any ideas?
Her's the pdncrash.log that was written when I tried to update at first:
Application version: Paint.NET v3.20 (Final Release Build 3.20.2902.32954)Time of crash: 15.04.2008 18:43:57
Application uptime: 00:00:19.4531250
OS Version: 5.1.2600.131072 Service Pack 2 Workstation x86
.NET Framework version: 2.0.50727.1433 x86
Processor: 2x "Intel® Core2 CPU 6400 @ 2.13GHz" @ ~2135MHz (DEP, SSE, SSE2)
Physical memory: 1023 MB
Tablet PC: no
Locale: pdnr.c: de-DE, hklm: de-DE, hkcu: n/a, cc: de-DE, cuic: de-DE
Exception details:
System.NotSupportedException: The given path's format is not supported.
at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath)
at System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[] str, Boolean needFullPath)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity)
at PaintDotNet.SystemLayer.Shell.RelaunchPdnHelperPart1(String& updateMonitorExePath)
at PaintDotNet.SystemLayer.Shell.Execute(IWin32Window parent, String exePath, String args, ExecutePrivilege execPrivilege, ExecuteWaitType execWaitType)
at PaintDotNet.Updates.InstallingState.Finish(AppWorkspace appWorkspace)
at PaintDotNet.Menus.CheckForUpdatesMenuItem.OnStateWaitingForInput(Object sender, EventArgs`1 e)
at PaintDotNet.EventHandler`1.Invoke(Object sender, EventArgs`1 e)
at PaintDotNet.StateMachineExecutor.OnStateWaitingForInput(State state)
Crash when updating from v3.22 to 3.30
in Troubleshooting & Bug Reports
Posted
Bumping after 1,5 years, b/c even with the latest 3.5 betas the automatic install fails while running the internal unzip (see above)