Bug #3374
TXM 0.8.2-0.8.3, the import form Font section is filled with the charts engine font preference
Status: | New | Start date: | 04/14/2023 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 80% |
||
Category: | Import | Spent time: | - | ||
Target version: | TXM 0.8.3 |
Description
Project doesn't seem to define a default font preference since 0.8.2.
Since Project extends TXMResult it searches in all preference nodes when retrieving a preference.
Therefore the chars engine font preference is used import Font section form.
Also the charts engine font preference is in in JFace StringConverter format (?|Font name|size|style|?|?|...) so it may lead to problem during import.
And in the Font section we can see the font in JFace format, e.g. "1|Lucida Sans Unicode|11.0|1|WINDOWS|1|-16|0|0|0|400|0|0|0|0|3|2|1|34|Lucida Sans Unicode;"
Solutions¶
WIP SJ:
1) set a default font preference in TBXPreference : "" should work -> nope the alternate nodes are tested before
2) Fix the alternate node qualifiers of the TXMPreferences class -> general fix for the other default preference values
3) Avoid keys with the same names3a) use prefixes -> may brake inheritence
3b) rename the identified keys :
- ChartsEnginePreferences.FONT = "font" -> "chart_font"
History
#1 Updated by Sebastien Jacquot 5 months ago
- Description updated (diff)
#2 Updated by Matthieu Decorde 5 months ago
- Description updated (diff)
#3 Updated by Matthieu Decorde 5 months ago
- Description updated (diff)
#4 Updated by Matthieu Decorde 5 months ago
- Description updated (diff)