On 2011-10-25 19:36, Pawel Sztromwasser wrote:
That I didn't know. So when no column mapping is provided for a
property, the project default is used (since the property is regarded as
not initialized, and not null). I also like the expression solution in
column mappings. It has an advantage
On 2011-10-25 19:36, Pawel Sztromwasser wrote:
I like one-click fix-it buttons (one is available for inheriting
annotations if I am not mistaken), and they would definitely speed up
work with BASE removing some of the repetitive interactions. If it is
possible to include them in the roadmap
Hello,
I was wondering if the project defaults are used in batch importing,
i.e. when a property is not specified in tab-delimited file but set as
default in an active project? I did a quick test and it didn't work, so
I thought I could suggest it. This way setting project properties
upfront
More feedback:
I've extensively used the no column-use project default
functionality, and I think it's logical to do it that way, but the
expression-based enhancement sounds like a good next step forward.
On Tue, Oct 25, 2011 at 1:01 PM, Nicklas Nordborg nick...@thep.lu.se wrote:
On 2011-10-25
That I didn't know. So when no column mapping is provided for a
property, the project default is used (since the property is regarded as
not initialized, and not null). I also like the expression solution in
column mappings. It has an advantage over a plugin parameter because it
allows to
