upCast RT 7.1 Build 1354 (Public Release)
*** upCast RT 7.1 Public Release ***
New Features
- UPL: new function get-color-component()
Changes & Improvements
Working with pipelines in both, top-level and sub-pipeline situations shows that in many cases, a Finalization setting of a top-level pipeline to show an error dialog conflicts with its usage as a sub- pipeline.
We therefore change the behaviour of pipelines with respect to logging as follows:
- For top-level pipelines, the Finalization presets (i.e. all values except for "custom") do NOT have any influence on whether the error dialog after an execution shows or not. The dialog always shows when there was at least an ERROR (ar at least a WARNING when the Finalization mode is set to "signal on warning").
- For sub-pipelines only, the finalization signal value is respected.
Additionally, the log messages a pipeline hands to its parent (when run as a sub-pipeline) is no longer filtered by the Finalization mode parameter, but by its Log level setting. (The former behaviour was actually a bug.)
The above has the advantage that during tests, you see any generated error messages in a pipeline (because it is a top-level one at that time), yet can configure the pipeline easily in a way to not cancel execution of a pipeline when used as a sub-pipeline.
We think this is the expected and a desirable behaviour. The old behaviour can still be emulated by using a custom finalization method.
- RTF Exporter: For CALS tables, we now issue an error when finding inconsistent colnum specifications.
- Commandline: StreamMungers should use a message template for stdout+stderr logging to easily intercept messages in custom finalization functions or filter on those messages
- Write \n always as line separator in preferences files to make written files identical regardless of platform
- Improve Java source generator for RunPipeline format: better comments, correct class usage example
- Ensure visibility of all opened windows on the main screen, with at least 60x60px visible. Important when opening pipelines created on a huge screen on smaller displays, so that they remain accessible.
- Displace new pipelines (File > New) by 20x20px from topmost window so all windows remain visible and grabbable instead of layering directly over each other.
- Export as Ant task: add extension ".xml" automatically when none is provided
Commandline: Allow array as value for Commandline module parameter and skip parsing it into the commandline parameters to use on System.exec().
This allows e.g. in UPL to specify the individual parameters clearly and easily, not needing to worry about all the quoting issues.
Fixes
- RTF Exporter: "float" generated an invalid set of RTF properties
- RTF Exporter: CSS style application does not take order of writing into account for style matches of the same weight, meaning that am applicable style with the same weight as another one might be applied before the former, even if it appears later in order of definition.
- Tables sometimes render show wrong in Word, although the source data structures are correct until actual serialization.
- RTF Exporter: We must not fill numbering gaps with default colspecs, but may do this only at the end when there are less colspecs than @cols specifies.
- UI: setting for included and excluded message IDs was not respected at all
- Passing ucdocs via commandline to GUI app not respected when determining empty pipeline creation flag
- Don't make new pipelines dirty by default. They should only be marked dirty when anything changes in them.
- Implementation of exists-var() and get-var() for realm variables must not trigger FATAL error when var does not exist.
- Converting UPL List to ArrayList on storing to pipeline variables does not work.