On 3/3/13 9:18 PM, jeremy rosen wrote:
> I sort of agree except that before cahnging anything we REALLY need to
> make spot-size more discoverable. Ctrl-mousewheel alone won't make it.
99% of all programs I use (DT is the 1%) use border drag to change the
size of a region.
This what I did in equ
very good point AlicVB, I had forgotten about that...
On Sun, Mar 3, 2013 at 10:00 PM, AlicVB wrote:
> Hi all,
> interesting discussion indeed. But please don't change too much things
> now in spot removal, as in a (near ?) future, this iop will use the
> masks tools...
> So we will need a more
Hi all,
interesting discussion indeed. But please don't change too much things
now in spot removal, as in a (near ?) future, this iop will use the
masks tools...
So we will need a more global discussion about that.
FYI, I have already this change working at home :)
thanks
Aldric
Le 03/03/2013 2
On Mon, Mar 4, 2013 at 9:18 AM, jeremy rosen
wrote:
>> yes.. and i would agree to your idea of just keeping it as it is.. but
>>
>> if for some reason most people aren't handy enough with a mouse to
>> hover over the circle and can't take the mental pressure to interpret
>> the highlighted circle.
> yes.. and i would agree to your idea of just keeping it as it is.. but
> if for some reason most people aren't handy enough with a mouse to
> hover over the circle and can't take the mental pressure to interpret
> the highlighted circle.. :) i think ctrl+zoom for the spot size is the
> less intr
hi all,
i hereby declare that we are in string and feature freeze in preparation of 1.2.
that means please don't push any new translatable strings to master or
change them (that's the ones in _("") ).
to give us a chance to make the release somewhat stable, please don't
introduce new features.
yeah, sounds reasonable. maybe we also need to revise the list of
modules visible by default in a new installation?
On Mon, Mar 4, 2013 at 8:58 AM, jeremy rosen
wrote:
> interesting idea... i'd like that
>
>
> On Sun, Mar 3, 2013 at 8:16 PM, Ulrich Pegelow
> wrote:
>>
>> Hi all,
>>
>> reading ne
On Mon, Mar 4, 2013 at 8:58 AM, jeremy rosen
wrote:
> I understand your point, but let me do a couple of counter argument
>
> * scroll is easier to discover than control-scroll, so it makes the various
> iop manipulations easier to find. (one could argue that zoom is more
> important, but see my n
On Sun, Mar 3, 2013 at 8:41 PM, Alexander Rabtchevich
wrote:
> GIMP complains:
> Unknown field with tag 18246 (0x4746) encountered
> Unknown field with tag 18249 (0x4749) encountered
> TIFF directory is missing required "ImageLength" field
>
> Also GIMP asks to select a page - is it a multipage ti
interesting idea... i'd like that
On Sun, Mar 3, 2013 at 8:16 PM, Ulrich Pegelow
wrote:
> Hi all,
>
> reading newbie reports on darktable it seems to be one of the most
> frequent complaints that is is difficult to keep overview of the iop GUIs.
>
> I assume that this is mostly due to the fact t
I understand your point, but let me do a couple of counter argument
* scroll is easier to discover than control-scroll, so it makes the various
iop manipulations easier to find. (one could argue that zoom is more
important, but see my next point)
* ctrl-mouswheel is a common shortcut for zoom, so
GIMP complains:
Unknown field with tag 18246 (0x4746) encountered
Unknown field with tag 18249 (0x4749) encountered
TIFF directory is missing required "ImageLength" field
Also GIMP asks to select a page - is it a multipage tiff?
Alexander Rabtchevich wrote:
> Hello
>
> Darktable produces 16-bit t
Hi all,
reading newbie reports on darktable it seems to be one of the most
frequent complaints that is is difficult to keep overview of the iop GUIs.
I assume that this is mostly due to the fact that currently users are
required to do some active housekeeping. If work on a iop is finished
the
Le 03/03/2013 19:54, jeremy rosen a écrit :
> How about using control mouse for zoom as in light table and normal
> scroll for iop specific action?
I would prefer mouse for zomm and control mouse for iop because Lr does
that and because I do far more zooming into the image than changing some
iop s
Am 03.03.2013 19:54, schrieb jeremy rosen:
> How about using control mouse for zoom as in light table and normal
> scroll for iop specific action?
>
I'd prefer it the other way round. There are not so many iops with mouse
wheel control. OTOH zooming in and out of the image is one of the most
fre
How about using control mouse for zoom as in light table and normal scroll
for iop specific action?
Le 3 mars 2013 17:16, "David Vincent-Jones" a écrit :
> I am glad that I am not the only one anoyed by this behavour ... Alt+
> Scroll (for instance) would be a great solution.
>
> David
>
> On 13
Hello
Darktable produces 16-bit tiffs, which are not recognized by argyll (it
doesn't understand compressed tiff). Also some image tags are wrong or
missed (GIMP 2.9 git also complains).
With respect,
Alexander Rabtchevich
---
I am glad that I am not the only one anoyed by this behavour ... Alt+
Scroll (for instance) would be a great solution.
David
On 13-03-03 04:16 AM, Moritz Moeller wrote:
On 2/3/13 10:11 PM, David Vincent-Jones wrote:
Spot removal really works well but I find that changing the spot size
conflic
On 2/3/13 10:11 PM, David Vincent-Jones wrote:
> Spot removal really works well but I find that changing the spot size
> conflicts badly with the image zoom and can be a tad frustrating. would
> it be possible to lock the image zoom while the spot module is open?
Bad idea imho. I zoom a lot while
FYI, I have proposed a fix for this. See pull request here:
https://github.com/darktable-org/darktable/pull/188
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --re
20 matches
Mail list logo
