I understand it can be troublesome, i did not realized it was a difference between GTK and qt too.
Myself i got screwed a few times, i set my filters get nice results after fine tuning stuff and then realize i was not outputting in a new layer so i had to restart everything from zero.
Even now that I know it doesn’t save the setting it happens to forget about it once in a while…
I don’t know how it could be managed, what previous guys posted seems ok for me, as long as i don’t need to worry about it anymore once set and since i always use the same output method to a new layer it will be fine for me.
For the dialogs remembering the paths it will be really nice to have this back, was very efficient before where not only it kept the path but also last LUT used, now i need to browse all folders again each time i restart gimp which doesn’t seems like a big deal but when you are used to previous method you realize how much more efficient it was of course, i would not mind if it remembers only the path and not the lut file used tho, will be more than enough for me already.
Thanks a lot for the last version and this new option :
Noticed that apparently only the newly favs added kept the settings, if only modifying the output option on a existing one it was not kept apparently,
but also found a easy way to modify all my existing favorites by editing the AppData\Roaming\gmic\gmic_qt_faves.json file and adding “outputMode”: 1 instead of 0 for output as new layer, really easy and quickly done.
Tank you so much for this new possibility, really great.
Edit : also possible to store a LUT direct path used as favorite in the gmic_qt_faves.json, or even better just the path of a folder where my LUT’s are all stored.
Actually, this is subject to changes in a few days.
We think that having a persistance of the input/output parameters for each filter is actually the best thing to have, including the favorites. So that should be the case in the future release.
This works well for me, noticed i could even change some things i was not able to do before, like the Fourier watermark directly having the watermark text i want, previously i always had to replace the “G’mic” default text by what i needed and never could keep my own watermark text stored, now it is possible to keep it and it’s great for the workflow.
Anyways as long as i have a way to keep settings remembered it is all good for me.
I’ve just posted new binaries today for the 2.0.0 pre-release version of G’MIC (link). It is intended to be the last pre-release before the final version planed for next week. If you have some time and motivation for testing these, we would be really grateful to get feedback from you. Most of the things we wanted to put in version 2.0.0 should be working as expected.
I’m also writing a quite comprehensive summary of all the features we’ve put into G’MIC these 12 last months. As you may imagine, this actually represents a lot of work
Thanks @MrQ, I’ve fixed the Sample image filter. Should be OK after you update your filters.
Yes, .ts files are being updated and should be available shortly on github. Any help for translating the two or three strings remaining will be appreciated
Ha yes, actually you are right, the link displayed on the download page is broken
Cannot fix this right now, as I’m having a long quiet week end, but I’ll be back and fix this on Monday !
Thanks for your report !
When I set preview off and then on, it doesn’t show the preview anymore, but the original. If I then change the zoom-factor, it shows the preview again. (edit: only in QT)
Can this please be corrected, so I can use preview off,on,off,on,off, on…, so I can compare? (this is solved with final release , thank you.)
I like that the zoom-factor is showed now. Is it possible that you can manual enter the zoom-factor in future releases? So I can, for example, enter 100% as zoom-factor?
Note that you can also press the right mouse button over the preview to quickly switch preview on/off. This is more convenient than using the checkbox for that particular task.
Yes, that should be possible in the next release, thanks for your suggestion
Could you please share this version of gmic-qt for GIMP 2.9 once again? I’ve tried to compile gmic 2.0.2 with latest gmic-qt for GIMP 2.9.2 and 2.9.4 and got the same errors as @sguyader before. Also, I found some patch for gmic_gimp_gtk.cpp, it allows to compile it, but plugin doesn’t work with protocol not supported message from the GIMP (both versions).
I really doubt the plug-in binary will work if it has been compiled with a version of the GIMP API which is not the same as the one you are using! I can compile the plug-in for 2.9 only on Linux, Ubuntu 16.04.
For other systems, I can’t do anything right now.
Of course I’m using GIMP 2.9 and trying to compile it for GIMP 2.9 with no luck (tried for versions 2.9.2 and 2.9.4). I’m getting these error messages:
src/host_gimp.cpp:63:9: error: ‘GimpLayerMode’ does not name a type; did you mean ‘GimpTransferMode’?
typedef GimpLayerMode GimpLayerModeEffects;
^~~~~~~~~~~~~
GimpTransferMode
src/host_gimp.cpp:66:23: error: ‘GIMP_LAYER_MODE_NORMAL’ was not declared in this scope
{ QString("alpha"), GIMP_LAYER_MODE_NORMAL },
^~~~~~~~~~~~~~~~~~~~~~
src/host_gimp.cpp:66:23: note: suggested alternative: ‘GIMP_RGB_COMPOSITE_NORMAL’
{ QString("alpha"), GIMP_LAYER_MODE_NORMAL },
^~~~~~~~~~~~~~~~~~~~~~
GIMP_RGB_COMPOSITE_NORMAL
src/host_gimp.cpp:67:24: error: ‘GIMP_LAYER_MODE_NORMAL’ was not declared in this scope
{ QString("normal"), GIMP_LAYER_MODE_NORMAL },
^~~~~~~~~~~~~~~~~~~~~~
src/host_gimp.cpp:67:24: note: suggested alternative: ‘GIMP_RGB_COMPOSITE_NORMAL’
{ QString("normal"), GIMP_LAYER_MODE_NORMAL },
^~~~~~~~~~~~~~~~~~~~~~
GIMP_RGB_COMPOSITE_NORMAL
src/host_gimp.cpp:68:26: error: ‘GIMP_LAYER_MODE_DISSOLVE’ was not declared in this scope
{ QString("dissolve"), GIMP_LAYER_MODE_DISSOLVE },
^~~~~~~~~~~~~~~~~~~~~~~~
src/host_gimp.cpp:68:26: note: suggested alternative: ‘GIMP_ERROR_CONSOLE’
{ QString("dissolve"), GIMP_LAYER_MODE_DISSOLVE },
^~~~~~~~~~~~~~~~~~~~~~~~
GIMP_ERROR_CONSOLE
src/host_gimp.cpp:69:24: error: ‘GIMP_LAYER_MODE_BEHIND’ was not declared in this scope
{ QString("behind"), GIMP_LAYER_MODE_BEHIND },
^~~~~~~~~~~~~~~~~~~~~~
src/host_gimp.cpp:69:24: note: suggested alternative: ‘GIMP_RGB_COMPOSITE_BEHIND’
{ QString("behind"), GIMP_LAYER_MODE_BEHIND },
^~~~~~~~~~~~~~~~~~~~~~
GIMP_RGB_COMPOSITE_BEHIND
… and so on. You wrote previously about special fork of gimp-qt that is different from c-koi/gmic-qt (dtschump/gmic-qt). But I can’t get access to it right now This is on Linux too (Fedora).
