A tethered shooting additional property cannot be edited or removed

Is there an existing issue for this?

• I checked and did not find my issue in the already reported ones

Describe the bug

In the tethered shooting module it is possible to extend the list of camera properties which can be adjusted before a capture is requested. Any additional property added to the last of camera properties using the ‘additional properties’ and ‘add user property’ interfaces can neither be edited nor deleted. There is no information in the manual on how this capability is to be used; one has to learn by trial and error. As a result unwanted or unusable entries appear in the list of properties, where vertical space is limited.

The issue is illustrated in the two attached screen shots. Shot ‘0' shows 2 additional properties: ‘my EC’ and a no label, unknown property. The name of the former cannot be edited and the latter cannot be removed. Shot ‘1' shows the result of an involuntary mouse movement when selecting a property. I would now like to change the selected property to the one I intended but there is no support for this: clicking on the large ‘O’ to the right of the selected property works once only; after an initial click this ‘button’ has no effect.

I note that there is zero response to my post on this topic on pixls.us. Perhaps the post to issue #2930 by ‘matrixik’ on 23 June 2020 explains why; he says:
"Yes, it would be great but from what I read on discuss.pixls.us and in some github issues tethering have now almost no one working on it. It's not rewritten like rest of DT so it's using stuff that was removed from other places so it's getting more broken over time. And it was almost removed completely from DT once, it survive only because one person said that he is using it in studio.”

I would be very disappointed to find support for tethering being removed from dt. Having learned how to use it enough, I find it to be tremendously useful in my now decades-long attempt to digitise my slide collection dating back to the 1950s. The alternatives - such as Entangle, gphoto2/gtkam, digiCamControl are not as productive, because they lack the deep integration with darktable that comes with the tethering module. None of the ‘tutorials’ or videos I find on the web mention the challenge of administering the synchronisation of the physical slide assets with the captured image, especially the tagging aspect of the end-to-end process. Those on-line articles are concerned only with configuring and using the kit, whether DSLR scanning or some alternative process. In contrast I am finding that capturing the image represents only about 20% of the tasks to be completed in a through digitisation work-flow. darktable’s asset management helps here considerably, so having a deep integration with tethering is most important.

Please keep it.

Steps to reproduce

Follow the process implied the the tethering module user interface to 'add user property' to the list of available, adjustable camera properties.

Expected behavior

darktable should allow CRUD (Create, Read, Update, Delete) not just C and R. The 'O' button in 'add user property' should be repeatedly usable.

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.4.1

What OS are you using?

Linux

What is the version of your OS?

Mint 22.3 and MX Linux 25.2; same issue on Windows 10

Describe your system

Issue exists when using Nikon D610 (Full frame DSLR) which has a very extensive list of properties which can be selected and with Fujifilm X-T3 with a limited set of additional properties, under either

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

nVidia GTX 3060 and GTX 1050; using default driver supplied by OS

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Start in darktable's tethering module, focusing on the “additional properties” and “add user property” interfaces. Reproduce the issue with a camera property, then verify that an added property can be edited, removed, and selected repeatedly; completion means full CRUD behavior works without leaving unwanted entries.