|Re: [scout-dev] Release Notes Eclipse Scout Trunk (Juno, 3.8.0)|
we fully agree. bug-specific resolution info that is not trivial should always be provided in the specific bug (what has been forgotten in this case (and now be corrected))
This information should be included on the bug. Splitting information about a bug and its resolution across different communication mechanisms makes it basically impossible for anybody to keep track of what you're doing. By extension, that
makes it very difficult for anybody else to participate in your project.
You are receiving this e-Mail because you are subscribed to Eclipse Scout Trunk.
BSI ticket #99'518
In a table with multi-line text support, the String cell-editor should overflow the cell's dimension to enhance usability.
It should be implemented a similar way as in Excel.
When editing such a cell, a smartfield-like popup comes up to enter text. If the row already spanned multiple textlines, the popup merges with the cell-editor's dimension so you do not realize it is about a popup.
In Swing, it is further possible to resize that popup (east, south). The default size of that popup can be changed by setting 'WidthInPixel' and 'HeightInPixel' on the String field. That would be done in the 'prepareEditInternal' method of the string column.
Release: Juno, 3.8.0
Update Site: http://download.eclipse.org/scout/nightly/update/
scout-dev mailing list
Description: S/MIME cryptographic signature