Project

General

Profile

Bug #11073

Text input is broken on OS X in 2.0.5

Added by Moritz Moeller almost 3 years ago. Updated about 2 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
Start date:
07/09/2016
Due date:
% Done:

100%

Affected Version:
2.0.5
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Right click on a slider which brings up the curve widget and allows text input. Text input doesn't work. It used to work fine in 2.0.4.

Isn't this covered by some tests that should prevent such high level stuff to be broken?

History

#1 Updated by Tobias Ellinghaus almost 3 years ago

Nothing changed in that code recently, so it's probably due to changes in GTK. Do you happen to know what version was bundled in 2.0.4 and what is shipped with 2.0.5?

#2 Updated by Moritz Moeller almost 3 years ago

No, I don't. But something it is unusable. It seems that keyboard events don't get through to the curve widget. When I right click a slider (say, exposure), the widget appears. Then I press '0'. No effect. I press '.'. This takes me back into lighttable mode. I press '5', this applies a 5 star rating to the image. I.e. instead of allowing me to enter 0.5 as an exposure value, all kinds of shit happens that will confuse the hell out of a normal user.

2.0.5 is no usable on OS X unless you never use keyboard input in darktable mode.

I also noticed that the font size for the modes (lighttable, darkroom, increases by ca 200% in 2.0.5). Shall I open another ticket for this or is this expected?

#3 Updated by Vincent Kee over 2 years ago

I have the exact same problem.

#4 Updated by Moritz Moeller over 2 years ago

Still unchanged when building latest master on OS X 10.11.6 on an up-to-date MacPorts installation.

#5 Updated by Roman Lebedev over 2 years ago

Moritz Moeller wrote:

Still unchanged when building latest master on OS X 10.11.6 on an up-to-date MacPorts installation.

Is this reported to the upstream yet? What did they say?
Since it just works in linux, my uneducated guess would be that it is gtk @ macosx problem

#6 Updated by Moritz Moeller over 2 years ago

I need to know where to report this. The upstream maintainer probably also needs more info; e.g. some pointers to source files to look at the code that manifests the issue. I'm not a DT dev, maybe you can point me to it?

#7 Updated by Rafa G. over 2 years ago

Moritz Moeller wrote:

I need to know where to report this. The upstream maintainer probably also needs more info; e.g. some pointers to source files to look at the code that manifests the issue. I'm not a DT dev, maybe you can point me to it?

Try to ask in IRC #darktable channel at freenode.

#9 Updated by Ben Beasley over 2 years ago

I’m having the same problem in Linux on Fedora 25, both with the system 2.0.7 package and with a 2.2.0.rc2 build. I’m not sure if it started with the update to Fedora 25, or with an earlier update in Fedora 24.

Depending on where my mouse cursor is, sometimes I even see the input cursor flashing on the popup “curve” window for the numeric parameter, but no input is ever accepted.

Edit: So, of course, just after commenting, I figured out something else important. The input still works on Fedora 25 (at least for 2.2.0.rc2, I’m not going to bother rolling back to the system version) in an Xorg session. It does not work under Wayland, which is the new default session! Maybe that makes it a different bug than the OS X issue, or maybe the problem is the same at its heart.

#10 Updated by Simon Rothen about 2 years ago

Text Input is working again with version 2.2.3 (don't know about the versions between and what code change fixed it though)

#11 Updated by Roman Lebedev about 2 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Good :)

#12 Updated by Roman Lebedev about 2 years ago

  • Target version set to 2.4.0

#13 Updated by Ben Beasley about 2 years ago

I’m sad to report this still doesn’t work on Fedora 25 under a Wayland session in Darktable 2.2.3.

Update: I’m not sure whether it was the recent update to Darktable 2.2.4, or a graphics-related update applied at the same time, but these controls work properly again at last on Fedora 25 under Wayland!

Also available in: Atom PDF