afterall I fixed it by posting Button event with valuators in driver
於 2010年02月28日 20:59, Sam Lin 提到:
yes I tried git version and it works nice with disabling event-history.
but still can't find how to make the driver work under enabling
event-history.
Thanks,
Sam
於 2010年02月28日 20:01,
1. Shrink wrap, up to version 2.6 on Ctrl+E, then on Ctrl+R, is now on
Ctrl+J.
2. Right-click in the image window no longer does anything.
3. When you open an image narrower than the menu bar, it is now flushed to
the left of the canvas, instead of being centered.
Just to be sure that all this is
On Tue, 2010-03-02 at 13:35 +0100, Olivier wrote:
1. Shrink wrap, up to version 2.6 on Ctrl+E, then on Ctrl+R, is now on
Ctrl+J.
Intentional.
2. Right-click in the image window no longer does anything.
Works just fine here.
3. When you open an image narrower than the menu bar, it is now
Yes, I will submit a proper patch. I'm new but I can figure it out.
I mainly wanted to get feedback whether it was desirable. I'm not clear
when a discussion of an enhancement should move to Bugzilla.
More testing reveals other issues and test cases:
First, most plugins have unguarded calls
Greetings,
A plug-in I'm currently developing may require writing a small file somewhere
to save its 'last-used' and 'default' settings: those settings can
theoritically use lots of memory (typically just a few bytes though), so I need
to allocate the appropriate amount of memory everytime the
Other plugins that save things go to the user profile directory root
(.gimp-2.6). For example, I have:
focusblurrc
pspirc
Check the source of any of these for examples.
Alternately, if there is not much data, you could use parasites.
some plugins also create/require a subdirectory under the
On Tue, 2010-03-02 at 08:01 -0500, lloyd konneker wrote:
Yes, I will submit a proper patch. I'm new but I can figure it out.
I mainly wanted to get feedback whether it was desirable. I'm not clear
when a discussion of an enhancement should move to Bugzilla.
More testing reveals other
On 2 March 2010 04:56, Sven Neumann s...@gimp.org wrote:
The current code is prepared for multiple algorithms as backend for the
segmentation tool. It's not foreseen that you switch between algorithms,
but that you pick one, but even that could probably be changed. As there
is currently only
Hi Thiago,
I agree that we should first merge the GSOC code from this year before
we start thinking of a new segmenter. Let me know if you need any
help. However, I think both a graph-cut-based segmenter and SIOX could
have a place in GIMP side-by-side. Graphcut-based segmenters and SIOX
Hi Gerald,
I believe we were writing emails at the same time, and you didn't get to
read my last one.
On 2 March 2010 21:49, Gerald Friedland frac...@gmail.com wrote:
First: Try any image that works well and add 80% noise. SIOX is pretty
good with noise.
Last time I tried Grabcut with such
10 matches
Mail list logo
