Re: [darktable-dev] Usermanual update for 2.2
Le 23/07/2016 à 10:52, Ulrich Pegelow a écrit : Dear all, I'd like to start an update of the usermanual to make it ready for 2.2. Let's begin by compiling a list of required changes. From my side following comes to mind and I added a proposal of whom might take care. Please and your proposals. * new module color check lut [Jo?] * new binary darktable-chart [Jo?] * new module liquify [Pascal?] * new module perspective correction [Ulrich] * various improvements for x-trans sensors [Dan?] * the "other" dropdown box [Tobias?] * new preferences tab for Lua options [Jeremy?] * updates to the collection module [Aldric?] * correction of outdated issues and factual errors [Roman?] * general style and proofreading [Ulrich] * . My idea is to start working now. Maybe we can have text for the new features complete by early September and have everything ready with all proofreading etc. by mid October. Ulrich ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org Hi Ulrich, I proposed 3 month ago a light improvement to paragraph 3.3.9.6 in #11005. Would you mind having a look at it ? and getting use of it ? Best regards, JP ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] French translation
Le 05/10/2016 à 14:11, Pascal Obry a écrit : Merci à tous! J'ai plusieurs propositions: - matrice de correspondance des couleurs - table de correspondance des couleurs - palette de couleurs - damier de couleurs - damier sélecteur de couleur - réglage de la palette - manipulation des couleurs - manipulation de la palette - mire de couleurs Il ne faut pas que le nom du module ne soit trop grand (sinon c'est coupé dans l'interface). Alors les 2 premières solutions sont pas adaptées bien que le texte soit bien descriptif. Pourquoi pas: - table correspondance couleurs ou - manipulation palette couleurs Qui comporte un caractère de moins que le nom de module le plus long actuellement. Personnellement je préfère la première avec "table" qui correspond bien à LUT. Voilà. Effectivement le premier est le plus explicite, mais il est très/trop long. Sinon, j'approuve ton choix. On peut peut être aussi tenter une abbréviation : table de corresp. couleurs JP ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Crashes with drawn masks
Darktable crash frequently when I use the drawn masks and I do many manipulations "up", "down", "change operator", and so on. Here is the console trace of a crash and the corresponding file /tmp/darktable_xxx.txt my configuration : darktable 2.0.7 on opensuse leap 42.1 Thank you for your great work ! jpv@penguin:~> darktable (darktable:4999): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory of theme oxygen has no size field (darktable:4999): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field (darktable:4999): Gtk-WARNING **: Theme directory of theme oxygen has no size field /* These warnings are always present, even when there is no crash*/ wait time 0,270269s try+ wait time 0,131340s mode r [New LWP 5000] [New LWP 5001] [New LWP 5002] [New LWP 5003] [New LWP 5004] [New LWP 5005] [New LWP 5006] [New LWP 5007] [New LWP 5008] [New LWP 5009] [New LWP 5010] [New LWP 5015] [New LWP 5016] [New LWP 5017] [New LWP 5018] [New LWP 5019] [New LWP 5020] [New LWP 5021] [New LWP 5022] [New LWP 5023] [New LWP 5024] [New LWP 5025] [New LWP 5026] [New LWP 5027] [New LWP 5028] [New LWP 5029] [New LWP 5030] [New LWP 5031] [New LWP 5032] [New LWP 5033] [New LWP 5034] [New LWP 5035] [New LWP 5036] [New LWP 5037] [New LWP 5038] [New LWP 5039] [New LWP 5040] [New LWP 5041] [New LWP 5042] [New LWP 5043] [New LWP 5049] [New LWP 5050] [New LWP 5051] [New LWP 5052] [New LWP 5053] [New LWP 5054] [New LWP 5055] [New LWP 5056] [New LWP 5057] [New LWP 5058] [New LWP 5059] [New LWP 5060] [New LWP 5061] [New LWP 5062] [New LWP 5071] [New LWP 5072] [New LWP 5073] [New LWP 5074] [New LWP 5075] [New LWP 5076] [New LWP 5077] [New LWP 5079] [New LWP 5080] [New LWP 5081] [New LWP 5082] [New LWP 5083] [New LWP 5084] [New LWP 5085] [New LWP 5086] [New LWP 5087] [New LWP 5088] [New LWP 5089] [New LWP 5090] [New LWP 5091] [New LWP 5092] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f5c65aa3469 in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_18EBSY.txt Erreur de segmentation ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.orgthis is darktable 2.0.7-127.3 reporting a segfault: #0 0x7f5c65aa3469 in waitpid () at /lib64/libpthread.so.0 #1 0x7f5c65d33760 in () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f5c65aa3870 in () at /lib64/libpthread.so.0 #3 0x7f5c65dd1d24 in () at /usr/bin/../lib64/darktable/libdarktable.so #4 0x7f5c65deaaeb in dt_masks_events_post_expose () at /usr/bin/../lib64/darktable/libdarktable.so #5 0x7f5c1ef2dc38 in expose () at /usr/lib64/darktable/views/libdarkroom.so #6 0x7f5c65e31dcd in dt_view_manager_expose () at /usr/bin/../lib64/darktable/libdarktable.so #7 0x7f5c65d8a931 in dt_control_expose () at /usr/bin/../lib64/darktable/libdarktable.so #8 0x7f5c65e07f90 in () at /usr/bin/../lib64/darktable/libdarktable.so #9 0x7f5c65015aae in () at /usr/lib64/libgtk-3.so.0 #10 0x7f5c651406fd in () at /usr/lib64/libgtk-3.so.0 #11 0x7f5c637ad247 in () at /usr/lib64/libgobject-2.0.so.0 #12 0x7f5c637c5418 in g_signal_emit_valist () at /usr/lib64/libgobject-2.0.so.0 #13 0x7f5c637c6062 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0 #14 0x7f5c6514eb95 in () at /usr/lib64/libgtk-3.so.0 #15 0x7f5c651501df in () at /usr/lib64/libgtk-3.so.0 #16 0x7f5c65150461 in () at /usr/lib64/libgtk-3.so.0 #17 0x7f5c64f685dd in gtk_container_propagate_draw () at /usr/lib64/libgtk-3.so.0 #18 0x7f5c64f686a2 in () at /usr/lib64/libgtk-3.so.0 #19 0x7f5c64f248b2 in () at /usr/lib64/libgtk-3.so.0 #20 0x7f5c65015aae in () at /usr/lib64/libgtk-3.so.0 #21 0x7f5c651406fd in () at /usr/lib64/libgtk-3.so.0 #22 0x7f5c637ad1bf in () at /usr/lib64/libgobject-2.0.so.0 #23 0x7f5c637c5418 in g_signal_emit_valist () at /usr/lib64/libgobject-2.0.so.0 #24 0x7f5c637c6062 in g_signal_emit () at /usr/lib64/libgobject-2.0.so
[darktable-dev] watermark simple text to small
Hi all, In the watermark module, I wanted to enter a one line text. I could not do it because my text exceeded the recording capacity of the area, which is 63 characters (but the input field in the module allows us to enter much more!). I checked the sources. In watermark.c, the two structures definitions: dt_iop_watermark_params_t and dt_iop_watermark_data_t include a 'char text [64]' member that exactly matches the found limit of 63 characters (+ EOL). In addition, the 'char' type assigned to this storage area must not match the UTF8 character set because every time I type an accented character in that area it further reduces the length. Would it be possible to increase the capacity of this area to 256 for example? Would it also be possible to change the type of this area so that it can accept accented characters? Can I help by offering a patch for this improvement? Best regards, JPV ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] new maintenance script purge_from_cache.sh
hi all,
The new maintenance script purge_from_cache.sh require a sub script
"common.sh" which is not provided.
line 25 : . "$(dirname "$0")/common.sh"
This script provides the ReadLink function
line 76 : library=$(ReadLink "${library}")
Where can I find the file common.sh?
thank you in advance for your help !
JPV
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] new maintenance script purge_from_cache.sh
Thank a lot !
JP
Le 08/04/2017 à 10:41, Hans Vanpee a écrit :
Hi Jean-Pierre,
You can find it in the Git repo.
Rgds,
Hans
Op za 8 apr. 2017 om 10:30 schreef Jean-Pierre Verrue
mailto:jean-pierre.ver...@laposte.net>>:
hi all,
The new maintenance script purge_from_cache.sh require a sub
script "common.sh" which is not provided.
line 25 : . "$(dirname "$0")/common.sh"
This script provides the ReadLink function
line 76 : library=$(ReadLink "${library}")
Where can I find the file common.sh?
thank you in advance for your help !
JPV
___
darktable developer mailing list to unsubscribe send a mail to
darktable-dev+unsubscr...@lists.darktable.org
<mailto:darktable-dev%2bunsubscr...@lists.darktable.org>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] possible data loss scenario
I was also trapped by the loss of focus. I found a very simple parade. I modified the shortcuts r, 1,2,3,4 and 5 for the light table and darkroom to CTRL-r, CTRL-1,..., CTRL-5. Since I have no problem! JP Le 25/10/2017 à 23:51, Patrick Shanahan a écrit : * Alexander Rabtchevich [10-25-17 15:07]: I've provided all the required steps in the thread before, step by step. Maybe it's better to spend some time for reading before blaming, isn't it? One of the user-cases is: start editing in some edit control (image size for export etc.) If the cursor occasionally leaves the control for some other control (except label), the latter steals focus and the keyboard input is not hooked by the original edit control one is actually typing in. If one is typing digits at that moment, they are interpreted as star rating. If any images are selected, that rating is mutually applied for them. If one have selected some images by some search criterion, including rating, applying wrong star rating can be fully destructive as that cannot be undone without the full knowledge about the set of affected images and their initial ratings. With respect, Alexander Rabtchevich Patrick Shanahan wrote: * Alexander Rabtchevich [10-25-17 12:12]: Hello Yesterday I've almost lost my data again. That time that hadn't happened because no images were selected. It's some kind of Russian roulette to change image size. With respect, Alexander Rabtchevich David Vincent-Jones wrote: Most noticed occurrence: Select items to print > double click to select current width for normal replace > type '0' > All selected images are now 'X' rated. I can only change width and height valued by backspacing. David cannot you provide steps and conditions which led to your "almost" condition that someone may provide a solution? only you can see and experience what is in front of you, other just have to guess or summons their crystal balls, or iron or perhaps your methods need examining. the *only* time I recall "almost" loosing data was when I was being quite foolist and in too much hurry mode. but I caught myself, re: almost. and I have "trash" disabled. I read the list and have read your posts and I have used dt extensively for several years and cannot recall more than once or twice having the mouse pointer "wander", but I use a track-ball. Maybe that is the difference. I did suggest you examine your methods and maybe you can minimize or stop the "cursor from leaving control" and stop almost losing data. and I cannot recall nor see that any "blame" has been assigned you, only a suggestion that your methods may be suspect. skin thin? ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Full metadata editor
Hi sam, A third solution would be to create tabs in the right column of the light table, like the 7 tabs in the right column of the darkroom. For example, a "files" tab, a processing tab, a metadata tab and a keywords tab. What do you think of that? JPV Le 22/07/2019 à 16:34, Sam a écrit : Hi, I'd like to start working on a more complete metadata editing interface. I've come up with two possible ways of doing this: 1) A pop up window - this gives a lot of space and flexibility to eventually add as many different metadata-editing features as we could possibly want. 2) Expand the current metadata editor module - I think I could squeeze quite a lot into there by splitting the fields up into different categories but it could quite easily become unwieldy and hard to use. My preference is for the first option, but it also doesn't really seem like the darktable way of doing things so I'm interested to hear some other people's opinions (I'm also open to any other suggestions, or opinions about if people actually want this feature added). Thanks, Sam ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
