-
Notifications
You must be signed in to change notification settings - Fork 165
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
Oddly located name and connector of Modelica.Electrical.Analog.Sources.SignalVoltage icon #2923
Comments
Since a picture says more than words: The changes are due to the clarified icon conventions and performed in #2215. |
Maybe I should clarify that I did not open this issue just because I dislike the new icon. I got issues because the new icon can result in misguiding rendering of existing model-diagrams if they are not manually adjusted (thus, it can "visually mess up existing user models" in a subtle way). The scenario I had was the following MSL 3.2.2 diagram (excerpt): Loading that model in MSL 3.2.3 shows: This is a misleading rendering, looking as if the output of It is a good intent to have all component names at the very same place according to some guideline; but, I think, if this results in disconnected connections just to satisfy the guideline, this is not a good idea. I mean, if we have three connections on three different sides, most user applications will just vertically and horizontally flip the component in its application contexts to avoid cumbersome connections. Such flipping will (should/must) take care of the component name; there is no reasonable way to enforce that the name is always above the component. It is much more important that the connections are fitting. In Dymola, we can adjust the component according to its usage context by flipping as follows: This is what will happen most times: to arrange the in- and outputs to fit the application context. For that reason I think that
but rather
|
First, I agree that Second, for the example you presented: No surprise: whenever icons change, they will look different. And yes, a changed look of an icon affects the appearance of every user model. So to me your example is a typical case, where the voltage source needs some additional horizontal spacing to the right to make it look good again. So with Summary: Either leave everything as it is (my preference) or switch to |
I would vote for If I am the only one annoyed by the new unconnected icon design, then I guess, it's as you say: leave everything as it is. Considering the little response so far, I say just close the ticket. It would be nice in the future though, if relentless following the design guide lines would consider practice also and avoid icons that fall apart with dangling connectors. As I stated above, one would anyway flip the component until its connections fit the application context; a rule like "component names must always be above the component" makes in the context of icons with only one connector-free side little sense since respective components will be flipped all the time anyway. It is the connector-free side the component name should be; if one wants the component name above, fine -- but put the 3 connectors on the other sides. |
Compared to MSL 3.2.2, the Icon of
Modelica.Electrical.Analog.Sources.SignalVoltage
changed in MSL 3.2.3. There are two changes that seem unnecessary and result in odd looking diagrams:v
input connector is hanging in the air, not close and above the rest of the icon. In MSL 3.2.2 it was next to the ellipse/rest of the icon.v
input connector and the ellipse, sort of above the actual icon. In MSL 3.2.2 it was just below the icon.I am wondering, are these changes intentional? It looks odd that the name is squeezed in-between the "actual" icon and an input connection. In diagrams the name locations are now flipped and the
v
input connections seem to hang in the air.The same changes are done for
SignalCurrent
. I can understand, that we may like to have all names above icons, but at the price to break off input connections that are then hanging in the air? This looks really ugly in diagrams -- actually it looks like a pending connection error either due to a connection not properly drawn but correctly modeled (i.e., in fact connected but not shown as such) or indeed with a loose end (i.e., connected to soemething that does not exist and just drawn).The text was updated successfully, but these errors were encountered: