Opened 6 years ago

Last modified 3 years ago

#5410 assigned defect

Properly indent dragged-and-dropped components

Reported by: Francesco Casella Owned by: Martin Sjölund
Priority: high Milestone:
Component: Interactive Environment Version:
Keywords: Cc:

Description

When dragging and dropping a component in a model, the corresponding declararion should be indented by 2 characters, according to the common custom of hand-written Modelica models

Attachments (2)

5410.mos (866 bytes ) - added by Adeel Asghar 6 years ago.
indented.mos (672 bytes ) - added by Adeel Asghar 6 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 by Francesco Casella, 6 years ago

Component: *unknown*OMEdit
Milestone: Future1.14.0
Owner: changed from somebody to Adeel Asghar

comment:2 by Adeel Asghar, 6 years ago

Status: newaccepted

I get the expected behavior. Do you have a use case where it is not indented properly?

comment:3 by Francesco Casella, 6 years ago

Try with the library attached to #5392, drag components from the Components library into a model put in some other package.

by Adeel Asghar, 6 years ago

Attachment: 5410.mos added

comment:4 by Adeel Asghar, 6 years ago

Component: OMEditInteractive Environment
Owner: changed from Adeel Asghar to Martin Sjölund
Status: acceptedassigned

Another bug in diffModelicaFileListings.

comment:5 by Martin Sjölund, 6 years ago

Not a bug. A feature you want. It just does diffs. It doesn't format new code for you :)

by Adeel Asghar, 6 years ago

Attachment: indented.mos added

comment:6 by Adeel Asghar, 6 years ago

I consider it a feature if it has a constant behavior. It does indent the code in some cases. See attachment:indented.mos

comment:7 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:8 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:9 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:10 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.