05-06-2018, 12:18 PM
Thanks Ofnuts.
Yes, a mistake (I have written these test filters in a hurry).
Corrected them.
Now the situation is:
- with the initial brush set to "None", the filter can be run repeatedly and not just only once as previously with the error you noticed.
- with the initial brush set to an existing one, still the filter shows up in the menu but does not show the parameters window when called (i.e.: does not start, it's uncallable).
INHO this means that 2.10 is unable to handle a brush initialized in a parameter.
This opinion is reinforced by the fact that the previous (erroneous) version of the filter with the parameter set to "None" did work properly only once, because in the absence of the ...context_pop() at the end, the filter was "remembered" by Gimp as having a predefined brush by default.
What do you think about?
Yes, a mistake (I have written these test filters in a hurry).
Corrected them.
Now the situation is:
- with the initial brush set to "None", the filter can be run repeatedly and not just only once as previously with the error you noticed.
- with the initial brush set to an existing one, still the filter shows up in the menu but does not show the parameters window when called (i.e.: does not start, it's uncallable).
INHO this means that 2.10 is unable to handle a brush initialized in a parameter.
This opinion is reinforced by the fact that the previous (erroneous) version of the filter with the parameter set to "None" did work properly only once, because in the absence of the ...context_pop() at the end, the filter was "remembered" by Gimp as having a predefined brush by default.
What do you think about?