[MLZ] New release
MLZ users will have noticed
a recent upgrade to the client.
The latest release incorporates two major improvements:
The latest release incorporates two major improvements:
- The code behind the right-side panel has been completely rewritten.188BET靠谱吗The original code was written before I fully understood how the Zotero UI itself works, and it showed - the new code is much more stable (and easier to work with from a programming standpoint).The multilingual menus are now both available under right-click, and various bugs in the old interface have been fixed.
- Legal support is now driven by a new system ofjurisdiction and court identifiers.Free-text entry is permitted for courts, but unrecognized entries are highlighted in yellow.Both recognized and unrecognized entries will render normally in citations.
A couple of thoughts (all of these coming from a Mac installation):
On (3), do you mean the labels?They should receive a border on hover.If that's happening, it's according to design, but I can see that it could be confusing.
The aim is to have a consistent operation for the multilingual menus (right-click, because it's available on all field types), and to provide a hint of which fields are multilingualize-able (and hence recognize a right-click on the label).I'm open to suggestions and mock-ups for how to represent that on the label.
Looks like the remaining issue is the weird extra space you're seeing below the Jurisdiction field.
https://twitter.com/fgbjr/status/565346395155345408
There is more space after Jurisdiction than after any other field.
I'll fix that glitch in the CSS, then get ahold of a local Mac to take a proper look.
Meanwhile, I've made a small change to the behaviour of the creator labels.When a creator is open for editing, clicking on the label will close the field, as it does for the others.Clicking on the label with fields closed opens the creator type selection menu as per normal.
I'm not sure how the change will be received, but close-on-label-click is a handy operation, and it seems nice for it to be available across all field types.