git commit 34e09b9af31
It happened because signal, parameter and parameter2 were static members of the Observer class.
git commit 34e09b9af31
Checking is done by proofreaders, but out of the group of German proofreaders, from what I can see only wmayer is active.HarryGeier wrote: ↑Sun Mar 03, 2019 8:10 am When iu translate or change a translation, will this be checked by an admin and then be released
Yorik, it seems that it is no longer possible in Draft to use the Tab key to switch from a coordinate field to another.Yorik the Magnificent wrote:ping
That.Is.Hillarious!NormandC wrote: ↑Sun Mar 03, 2019 3:38 pmTIL: with the proper user_id in the first quote tag, you can write anything for the nameYorik the Magnificent wrote:ping
I couldn't find what the Tab key does in Draft edit mode... If this is related, it completely breaks usage of coordinate fields as you have no choice but to click in each field to make it active. What's odd, it does not affect the ShapeString UI, in there we can continue to use Tab to switch from one field to another.
It works if you activate the Z field then with Shift+Tab you can switch to Y and X. It's just when you start from the X field you cannot go down. What also works if you activate the Y field and then press Tab. So, it looks like the X field is a dead end.NormandC wrote: ↑Sun Mar 03, 2019 7:01 pmI couldn't find what the Tab key does in Draft edit mode... If this is related, it completely breaks usage of coordinate fields as you have no choice but to click in each field to make it active. What's odd, it does not affect the ShapeString UI, in there we can continue to use Tab to switch from one field to another.
I only vaguely read the discussions and it might end up not being related. But this feels related to changed behavior you described:NormandC wrote: ↑Sun Mar 03, 2019 7:01 pm I couldn't find what the Tab key does in Draft edit mode... If this is related, it completely breaks usage of coordinate fields as you have no choice but to click in each field to make it active. What's odd, it does not affect the ShapeString UI, in there we can continue to use Tab to switch from one field to another.
Apologies, it does break that behaviour to cycle UI focus. The tab key cycles through selectable objects, this allows you to snap to different objects or select different objects. Tab can change to another key, or alternatively the fields can have shortcuts of their own (X jumps to the x field, Y jumps to the y field, etc). This change is part of a series of changes which implement more granular editing of draft objects and a slow incremental cleanup of the draft code, and it needs polish and so more progress would have to wait until after v0.18 is released.triplus wrote: ↑Sun Mar 03, 2019 8:58 pmI only vaguely read the discussions and it might end up not being related. But this feels related to changed behavior you described:NormandC wrote: ↑Sun Mar 03, 2019 7:01 pm I couldn't find what the Tab key does in Draft edit mode... If this is related, it completely breaks usage of coordinate fields as you have no choice but to click in each field to make it active. What's odd, it does not affect the ShapeString UI, in there we can continue to use Tab to switch from one field to another.
https://github.com/FreeCAD/FreeCAD/pull/1943