Partha 2.9.6 in Windows 7

[mholder]

I'm working in Windows 7 for a bit and I really want the 2.9+ version of Gimp.  I use Patha's portable version so it won't mess up anything in my system.  Anyway, I spent so time getting it set up the way I want, adding brushes and other scripts etc.

Lots of my scripts and plugins worked fine until I put a .py script into the plugin folder.  This one:
http://registry.gimp.org/node/20069

After that, the Gimp wouldn't even start.  I removed the .py file and still it wouldn't work.  I had to remove the entire 'portable' folder and start over.  In the portable version the 'portable' folder is like the .gimp2.8 folder, where all the brushes, scripts, etc folders are.

This raises 2 questions:

First, does anyone know why something like this would happen?  And secondly, I read somewhere that all .py scripts need to go in the 'plugin' folder.  Really?  Is this a requirement or just a recommendation?

[rich2005]

(09-14-2017, 03:04 PM)mholder Wrote: I'm working in Windows 7 for a bit and I really want the 2.9+ version of Gimp.  I use Patha's portable version so it won't mess up anything in my system.  
--snip--
First, does anyone know why something like this would happen?  And secondly, I read somewhere that all .py scripts need to go in the 'plugin' folder.  Really?  Is this a requirement or just a recommendation?

More than a couple of things.

A plug-in either something.py or something.exe and any associated something.dll goes in your Gimp profile plug-ins folder.

For users that do not know where that is, find the exact location using Edit -> Preferences -> Folders -> Plug-ins.

Using a portable version, makes this location variable, but I installed Partha Gimp 2.9.6 portable under C:\ and it looks like this. 
Too many screenshots so not  in-line https://i.imgur.com/Xrdj9k4.jpg

Next one: 
The smooth-path plug-in is not python something.py it is a compiled plug-in something.exe
The plugin you get from http://registry.gimp.org/node/20069 is 32 bit and Gimp 2.9.x is strictly 64 bit. However I have one of those in my archive. It is attached as a zip file, remember to un-zip it. 
Goes in the plugins folder as smooth-path-64.exe https://i.imgur.com/1pLl3rw.jpg

Just to show it still works:
Right click in the paths dialogue to bring up the context menu -> at the bottom click smooth path -> brings up the settings.
https://i.imgur.com/shUcMVO.jpg

Works and pops up a info message https://i.imgur.com/cvgPZ8V.jpg

Want to suppress those messages, add --pdb-compat-mode=on at the end of the launcher (if you made one) https://i.imgur.com/7DKob4h.jpg

[mholder]

edit.  Hold on I get errors now when it loads . . . let me check something

I thought it was a .py file, but it was a Linux version that I pasted in there.
Still, using your version I get an error when Gimp starts

https://imgur.com/a/fV52v

I get these errors all the time with Partha's version.

[Ofnuts]

That plugin is a C file, so it has to be compiled.

Plug-ins go in "plug-ins", the only thing that goes in "scripts" is the script-fu scripts (ending in .scm).

[rich2005]

(09-14-2017, 07:32 PM)mholder Wrote: edit.  Hold on I get errors now when it loads . . . let me check something

I thought it was a .py file, but it was a Linux version that I pasted in there.
Still, using your version I get an error when Gimp starts

I can get that error as well.



..but only if I have the 32 bit version installed

1. Make sure you remove all traces of the old version. Then add the 64 bit version.

2. Apart from the different name, the file size is different, check that
32 bit: smooth-path.exe - file size 37,699B
64 bit: smooth-path-64.exe - file size 47,104B

3. You did unzip the file? y/n

4. Where are you putting the plugins? For the Partha portable it is
some-path-depending-where-installed\Gimp-2.9.6-std\portable\plug-ins

Quote:I get these errors all the time with Partha's version.

If you get that message all the time for various plug-ins then you are using non-compatible (probably 32 bit) plug-ins. Not everything will work with Gimp 2.9.x even some of the python plugins, for example layerfx.py is one.

[mholder]

Hmmm. I though it was your 64bit version that I tried. I guess I mixed them up, but it does work now. THanks for your help.

---

(09-17-2017, 12:17 PM)mholder Wrote: Hmmm.  I though it was your 64bit version that I tried.  I guess I mixed them up, but it does work now.  THanks for your help.

"3. You did unzip the file? y/n"
I'm incompetent, not stupid.

[rich2005]

(09-17-2017, 12:17 PM)mholder Wrote: Hmmm.  I though it was your 64bit version that I tried.  I guess I mixed them up, but it does work now.  THanks for your help.
"3. You did unzip the file? y/n"
I'm incompetent, not stupid.

Did not imply that, it has been known to happen, especially with Windows File Manager maybe hiding the file extension.

Pleased you got it sorted.

[mholder]

@rich2005 just messing around.

I noticed this:
https://www.gimp.org/downloads/devel/
Gimp 2.9.6 with a Windows installer? What? It has been some time since I exclusively used Windows, but the last I remember, I needed to use another OS or Partha's version to try out the Windows version. I distinctly remember having to use Partha's 2.7 to get the single-window mode.

???
This must be a new thing and I hope the Gimp developers keep posting a Git-free, already compiled Windows version.

[rich2005]

Quote:..This must be a new thing and I hope the Gimp developers keep posting a Git-free, already compiled Windows version.

It is a new departure, the first time the developers have posted a compiled Windows Gimp dev. version on their site.

https://download.gimp.org/mirror/pub/gimp/v2.9/windows/

Previously it was up to others (partha / samj) ... who provided a compiled development versions.

It is more traditional, opens a debug window but that can be minimised or sits in the background. Unlike Parthas' it is basic Gimp, no extra plugins, just the tools expected in a standard Gimp. All can coexist, this a Win 7 VM with Gimp 2.8 / Partha Gimp 2.9.6 / gimp.org Gimp 2.9.6 https://i.imgur.com/CSQt6tj.jpg