Hi Dinasset,

I installed contactsheet in a nearly fresh windows 7 ultimate 64 bits machine as virtual machine in virtual box: not working. Pythonw.exe crashes. GimpPDBProgress-callback crashes.
I don't know the problem yet but it could be python related.

But a lot of more succes with Indexprint.
Steps I have done.
1. Already installed was Python 2.7 32bits but Gimp uses his own Python interpreter
2. Installed Gimp 2.8.20 with default settings
3. Downloaded gimp-extensions v2.8.20150403
4. Start Extension pack and installed only Indexprint (this one is v4 development). It will be installed in the user\gimp\plugin directory.

Starting Gimp and Indexprint: working

Copied my Indexprint development (on Linux) dir into this machine: working like a charm. So I have attached the latest Indexprint. Backup/rename your old Indexprint.py and Indexprint directory just in case. Unzip the file and copy the contents in the same dir. Linux users can use the file too.

Remember: you will see new possibilities and a preview window. The preview window is not working correctly other added possibilities may not work at all.

Thanks moroquendo.
I did what you suggested: "Backup/rename your old Indexprint.py and Indexprint directory just in case. Unzip the file and copy the contents in the same dir."
The new version provided does not work (parameters window does not show up).
Hence I restored the one installed with the extensions pack yesterday (which BTW is v.4 development also). This one runs OK.
Thanks anyhow.

Hi Dinasset,

Can you look for me in start -> configuration --> (installed)programs if Python 2.7 PyGTK 2.24 is installed?? And what other kind of Python is installed.

This is what I have

I doesnot mean that. Assuming you are on windows: start button --> configuration --> (installed) programs

As "installed program" it does not appear (only Python appears)

Installed (standalone) Python is: 2.7.12.
But normally this is not required by Gimp, Gimp uses its embedded Python.

Hi Dinasset,

Really good news I hope. Found on the microsoft side a windows10 home/pro 32/64 bits iso. Downloaded the english iso and install home 64 bits edition in virtualbox.
Install Gimp 2.8.20 default, and try to start Gimp: running. Create three pictures of .xcf, .jpg and .png.
Closing Gimp and installing latest version of Indexprint, start Gimp and Indexprint: crash. Missing gtk/gtk.glade library.
Install libglade-2.0-0.dll into the bin directory of Gimp, start Gimp and Indexprint: running. All three pictures were read correctly.

Perhaps you need additional installation files for exif information, raw and ps/eps files. I have not tried/tested it yet.

Attached the libglade-2.0-0.dll I use. Do not use this file in Linux.

Sorry, still not working on my PC, restored the previous version.

Can you see it in the file menu?
If yes does it not start?
To see what is happening do the following:
1. open command prompt (admin)
2. cd\
3. execute the following line: c:\gimp-2.8.exe > error.txt 2>&1, assuming gimp is in your path.

If path not set: c:\"Program Files"\"Gimp 2"\bin\gimp-2.8.exe > error.txt 2>&1

Gimp will start, start Indexprint and quit Indexprint and Gimp.
In the root you will find a file called error.txt. Read it.

Indexprint for Linux users.

I tried two distributions: Kubuntu (16.04.2) and Xubuntu (16.04). Both fresh installed in a VM (virtualbox) with default options. After installation updated both installations. Because Discover caused problems I installed synaptic package manager (apt-get install synaptic) in both installations. After installation of synaptic I installed Gimp 2.8.16 (later I will upgrade to 2.8.20) with the package manager including all dependencies. Copied the latest Indexprint into gimp/user/plugin folder. Testing if Gimp runs and that was oke. Starting Indexprint let the plugin crash: gtk/gtk.glade is missing. Quit Gimp.

Installing python-glade2 2.24.0 GTK+ bindings to Glade (including all dependencies) with the package manager solves the problem: Indexprint runs as expected.

What I didnot have tested is exif information, ps/eps and raw files. It is possible that you have to add a few additional programs like UFRAW and pyexiv2.

Indexprint for Windows users.

It was recently published at gimpscipts.net Indexprint 3.34 for Windows and Gimp-2.10.22/23.
For Gimp-2.10 there is no need to install additional libraries (glade.pyd, libglade-2.0-0.dll, libxml2.dll - required are already installed)
Diego described the problem in a comment.
I also use the Samj version - but it works fine.
Could any "brave" user of a portable Samj version try this plugin?

Little bit surprised that I found my plugin on gimpscripts.net published.
Is gimpscripts.net the successor of gimp registry??

Hope that Sylvie ("Samj") could personally analyze the problem I found.
I say that because not much time ago I found a problem on G'mic Voronoi which was ONLY confirmed by Sylvie, so that now we have a G'mic Voronoi running. That problem was completely different and related to Windows acceptable special characters. This one (I ONLY GUESS) could be related to the fact that Indexprint "thinks" to run in a standard Gimp environment, while Samj's environment is self-contained and all pieces must be inside the package, hence if Indexprint (IDK) creates pieces after the first run outside that environment it could create conflicts: only a guess.

I tried running Indexprint V3.34 with SamJ portable Gimp 2.10.23 without success but it shows up in the file tab. I tried gimp.exe --verbose --console-messages for debugging but for some reason it doesnot work. I'm unfamiliar with SamJ product how to get debug output on my console.

Thanks for testing. Sorry I can't help with debugging.
But what happened to me is that, after having included in the plug-ins, it worked perfectly (as I knew), but after a close/restart of Gimp, the loading process was "disturbed" and "lost" all my plug-ins links, giving a sequence of panels (not seen normally during loading) and I had to recreate my links (obviously after removing indexprint) to reset the situation. This gave me the impression that "something" has been added during the first run which disturbed the package.

Yes and No.
The Gimp Registry went down and to keep valuable assetts online another one was started by a different person. All the scripts and plugins from the way back machine are there as well. Lots of work has been put in to recovery, making new add - ons and converting older scripts and plugins so they can be used in the 2.10 version of Gimp. Then there's even more work that I do not know about.

Indexprint doesnot add anything except for an errorlog, if an error occur, and a config file to remember your settings. But all inside Indexprints directory. The other thing what is added is telling Gimp that Indexprint should be added to the file-print menu and within the helpsection->plug-in-browser.

Thank you Sallyanne I didnot know that another person started a new kind of Gimp Registry. I will have a closer look at it these days.

In actuality, gimpscripts.net is a continuation of gimpscripts.com. When GnuTux was no longer able to continue with the original site, MareroQ and I decided to get something "out there" for users who had migrated to GIMP 2.10. We both just add scripts given to us by authors, and MareroQ repairs and updates older scripts/plugins for 2.10.

Also, I should point out that all comments posted to gimpscripts will likely go unanswered as I'm not even sure MareroQ is aware there are comments. I simply allow the comments to be posted and if there is anything I can do, I will reply (most likely bad links, etc) Technical issues with scripts/plugins are MareroQ's area of expertise.