Anonymous | Login | 2021-01-17 11:34 UTC | ![]() |
My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001044 | OMNeT++ | simulation kernel | public | 2018-06-15 11:41 | 2018-06-15 11:44 | ||||||||
Reporter | levy | ||||||||||||
Assigned To | andras | ||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | confirmed | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001044: The image-path config cannot be merged with --image-path command line argument | ||||||||||||
Description | In INET, if an example contains specific images in its folder, then there's no way of specifying the 'image-path' in the omnetpp.ini, because the default INET '--image-path' command line argument overrides it. It would be nice to have a way of saying ${next} or something like that to refer to the value of the next applicable configuration entry. This would allow one to write '--image-path=${next};bar' in the command-line and 'image-path=foo' in omnetpp.ini resulting in the 'foo;bar' image path. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
![]() |
|||
Date Modified | Username | Field | Change |
2018-06-15 11:41 | levy | New Issue | |
2018-06-15 11:41 | levy | Status | new => assigned |
2018-06-15 11:41 | levy | Assigned To | => andras |
2018-06-15 11:44 | levy | Status | assigned => confirmed |
Copyright © 2000 - 2021 MantisBT Team |