-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microcontroller icon text and font size #186
Comments
@sjoelund Did you had a look on this? |
Changing size to 0 would probably work fine (renders in almost the exact same size in OMEdit). Odd that each tool has a vastly different size for 30 pt though. SimulationX looks like it's 200~250 pt. The Real-time block is rendered decently in all tools and that uses size=0 for the font size. |
Yes, strange indeed. |
I believe the problem is the extent interpretation for font size > 0. It looks like its size can be neglected and is only considered for font size = 0. |
Yes, but that doesn't answer why the font size is so different in the different tools... |
Fixed font size is similar for Dymola and SimulationX. What looks different is the vertical size of the line break. model A
annotation(
Icon(
graphics={
Text(
extent={{-450,450},{450,-450}},
lineColor={28,108,200},
fontName="Arial",
textStyle={TextStyle.Bold},
textString="ABCD\nABCDEF",
fontSize=30),
Rectangle(
extent={{-100,100},{100,-100}},
lineColor={28,108,200})}));
end A; |
FYI: I'll file a SimulationX ticket for neglecting the extent in case of an absolute font size. |
This fixes modelica-3rdparty#186, where fonts are displayed in different sizes in different GUIs when the font size is absolute.
This fixes modelica-3rdparty#186, where fonts are displayed in different sizes in different GUIs when the font size is absolute.
This fixes modelica-3rdparty#186, where fonts are displayed in different sizes in different GUIs when the font size is absolute.
The font (size) in icon Modelica_DeviceDrivers.EmbeddedTargets.AVR.Blocks.Microcontroller is intrepreted differently in three tested tools:
Dymola 2017 FD01
MWorks Sysplorer 2016
SimulationX 3.8
Not sure what the desired behaviour is and if this is a MLS issue actually.
See #170 for the general issue on MCU support.
The text was updated successfully, but these errors were encountered: