Improved MrQ add-on manager (dinasset's request)

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

akovia wrote:

ofnuts wrote:

Hmm. What do you mean by "lock the layers group open"? I have no problem manipulating layers and opening/closing groups when the script is displaying a window.

Also, in typical usage, you don't keep it permanently open...

Well I don't leave it open. If it is used at all then I am unable to open or close layer groups until I restart gimp. Even if I don't actually use the manager and just open and close it. I am at a loss on what to check for.

All the cleverness of the plugin is that it only exists while the window in up:

Attachment:

PythonPluginProcessTree.png [ 12.54 KiB | Viewed 2040 times ]

When you close the window the process should be removed from memory (and then I don't explain why it would mess with user interactions at that point...). So that would be the first thing to check.

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

Well I've tried removing all plugins except the Brush Manager and this still happens. I'm not completely lost around the command line but I'm not sure how to troubleshoot this further.

Just so it's clear what's happening..
https://dl.dropboxusercontent.com/u/935 ... anager.mkv

Any advice is appreciated.

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

After closing the addonManager window, execute:

Code: Select all

ps -eaf | grep addonCollectionManager

Is there a python process listed?

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

ofnuts wrote:

After closing the addonManager window, execute:

Code: Select all

ps -eaf | grep addonCollectionManager

Is there a python process listed?

None at all, which means something is changed maybe? I don't know how layer groups work so I don't understand how they could be affected. I also tried changing my theme back to the standard theme instead of small on a hunch but that didn't work either.

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

What is your version of Python? And of PyGTK?

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

ofnuts wrote:

What is your version of Python? And of PyGTK?

$ python
Python 2.7.3 (default, Feb 27 2014, 19:58:35)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gtk
>>> gtk.pygtk_version
(2, 24, 0)

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

Roughly same here:

Code: Select all

python
Python 2.7.3 (default, Feb 27 2014, 19:37:34) 
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gtk
>>> gtk.pygtk_version
(2, 24, 0)

Which window manager? Unity, Gnome, KDE, LXDE, other?

To tell if its PyGTK related:

1) use any of the tricks in the readme file to have Gimp rerun the registration
2) do not start a manager window
3) check if you still have the problem (the registration will make the plugin run but not open any windows)

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

ofnuts wrote:

Which window manager? Unity, Gnome, KDE, LXDE, other?

XFCE 4

To tell if its PyGTK related:

ofnuts wrote:

1) use any of the tricks in the readme file to have Gimp rerun the registration

Backed up then deleted pluginrc. Everything re-registered but still same thing.
A few errors but nothing looked serious to me.

ofnuts wrote:

2) do not start a manager window
3) check if you still have the problem (the registration will make the plugin run but not open any windows)

Not sure what you mean here or how to do it. There is an option in gimp for no UI --no-interface, but I doubt that's what you mean.
If you mean don't start the brush manager then I don't have any way to check if it works so I'm a bit confused.

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

The manager isn't there permanently, so the only explanation of its responsibility in your problems is that it does something that outlives it in the Gimp environment. Above it has run as part of the registration process, but without creating any windows. So by testing if your problem is there without opening one of the manager windows we can tell if the problem could be is in the general code or in the PyGTK one.

This said, if gimpfu3 doesn't work, remove it, because that one also deals with the GTK environment.

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

ofnuts wrote:

The manager isn't there permanently, so the only explanation of its responsibility in your problems is that it does something that outlives it in the Gimp environment. Above it has run as part of the registration process, but without creating any windows. So by testing if your problem is there without opening one of the manager windows we can tell if the problem could be is in the general code or in the PyGTK one.

Well I deleted all plugins except the manager and deleted the pluginrc again. Opened an image and checked that I could indeed open and close layer groups and it works fine. Then I opened the brush manager and didn't change anything and just closed the window. The layer groups are locked now.

ofnuts wrote:

This said, if gimpfu3 doesn't work, remove it, because that one also deals with the GTK environment.

I went ahead and removed it from my backup plugins. I just installed this recently but haven't had time to troubleshoot it.

This is seriously strange isn't it? LOL
Anyway, I am very thankful for your help. I'll try anything you can think of.

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

The only difference I can think of is your XFCE desktop. I'm not suggesting that you change it, but if you know somebody else who uses both Gimp and XFCE, you can try to have him/her install the plugin and see if it produces the same problem.

akovia · **Joined:** Jan 15, 2013 **Posts:** 133

ofnuts wrote:

The only difference I can think of is your XFCE desktop. I'm not suggesting that you change it, but if you know somebody else who uses both Gimp and XFCE, you can try to have him/her install the plugin and see if it produces the same problem.

I pretty embedded in XFCE as I've used it for years now so that's really not an option. I guess I'll ask on the list and hope someone might be able to help there. I appreciate your time on this.

Cheers.

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

@ofnuts. Do I open the addonmanger to edit this. I am quite leary about it, I am afraid I will mess up my brushes sets, they work perfectly with your addonmanager.

Quote:

Ofnuts... addon Manager

If not done already, you have to make sure the addonCollectionManager.ini in the plug-ins directory has the fonts support enabled:

[all]
enable: brushes gradients fonts patterns scripts

This is not enough, due to the way Gimp checks if plugins have changed, it will not notice the change. See the REGISTRATION note in the readme file for the various techniques to make Gimp rerun the registration code of the plugin. If you are on Linux, you can also just use the "touch" command on the .py file in a terminal session:
Code: Select all
touch ~/.gimp-2.8/plug-ins/addonCollectionManager.py

This will bump the timestamp to "now", and Gimp will rerun the registration.

I tried this: touch ~/.gimp-2.8/plug-ins/addonCollectionManager.py in terminal root but it didn't do anything.

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

molly wrote:

@ofnuts. Do I open the addonmanger to edit this. I am quite leary about it, I am afraid I will mess up my brushes sets, they work perfectly with your addonmanager.

Quote:

Ofnuts... addon Manager

If not done already, you have to make sure the addonCollectionManager.ini in the plug-ins directory has the fonts support enabled:

[all]
enable: brushes gradients fonts patterns scripts

This is not enough, due to the way Gimp checks if plugins have changed, it will not notice the change. See the REGISTRATION note in the readme file for the various techniques to make Gimp rerun the registration code of the plugin. If you are on Linux, you can also just use the "touch" command on the .py file in a terminal session:
Code: Select all
touch ~/.gimp-2.8/plug-ins/addonCollectionManager.py

This will bump the timestamp to "now", and Gimp will rerun the registration.

I tried this: touch ~/.gimp-2.8/plug-ins/addonCollectionManager.py in terminal root but it didn't do anything.

You should do that with your id, not as root. '~' is the home directory of the current user...

What is the date of your "pluginrc" file (Gimp's directory) and of ~/.gimp-2.8/plug-ins/addonCollectionManager.py?

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

The only date I can find on this is Sean Bogie, MareroQ, Ofnuts 2013
I downloaded it about a year ago when you last revised it.
It is called /home/molly/.gimp-2.8/plug-ins/addonCollectionManager-3.0.py

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

molly wrote:

The only date I can find on this is Sean Bogie, MareroQ, Ofnuts 2013
I downloaded it about a year ago when you last revised it.
It is called /home/molly/.gimp-2.8/plug-ins/addonCollectionManager-3.0.py

I'm taking about the date, as indicated by your file manager:

Attachment:

acm.png [ 9.71 KiB | Viewed 2163 times ]

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

02/07/2014 I notice you have the py one, I have the 3.0.py

viewtopic.php?p=149112#p149112

ofnuts · **Joined:** Oct 25, 2010 **Posts:** 4812

This is just an example... this is my working version, on which I tack a version number when I publish it.

The important bit is to have Gimp re-register the plugin. This will happen under several conditions, as explained in the readme, in the REGISTRATION note.

Additionally, on Linux, you can use the "touch" command so that the .py becomes more recent than the pluginrc file as shown by their respective file dates in your file manager.

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

ofnuts, will will please either do me a screen shot or explain where I type in this touch command, I have looked all over and even googled it. All I get is what is and does but doesn't tell me where to type it. I looked in my user plug-ins and all over.
I told you I was a techie nerd, ask me how to build a house and I can tell you every step.

Odinbc · **Posted:** Tue Sep 16, 2014 12:13 pm **(#160)**

molly wrote:

ofnuts, will will please either do me a screen shot or explain where I type in this touch command, I have looked all over and even googled it. All I get is what is and does but doesn't tell me where to type it. I looked in my user plug-ins and all over.
I told you I was a techie nerd, ask me how to build a house and I can tell you every step.

Open a terminal window in the dir of the file or cd the dir of the file.
Example (without options) for updating the access and modification times to the current time.

Code: Select all

touch filename.py

To confirm last modification time,

Code: Select all

date -r filename.py