You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If boolean parameters are adjusted within the TOPP tool framework, the framework attempts to set the flags explicitly, which is not expected by TOPP tools and leads to errors:
true values:
Current Output: -myflag true
Expected by TOPP: -myflag
false values:
Current Output: myflag false
Expected by TOPP: (omission)
It seems like we cannot distinguish boolean values from string values from the respective ini files (#59). Thus, for FLASHViewer we went with rules for the parameters values "true" and "false" (see d1a85b9). However, this solution could cause issues in scenarios where the values "true" or "false" should be actual strings.
I would assume that this a rare case but also wanted to see if anyone else has another opinion?
The text was updated successfully, but these errors were encountered:
If boolean parameters are adjusted within the TOPP tool framework, the framework attempts to set the flags explicitly, which is not expected by TOPP tools and leads to errors:
true
values:Current Output:
-myflag true
Expected by TOPP:
-myflag
false
values:Current Output:
myflag false
Expected by TOPP: (omission)
It seems like we cannot distinguish boolean values from string values from the respective
ini
files (#59). Thus, for FLASHViewer we went with rules for the parameters values"true"
and"false"
(see d1a85b9). However, this solution could cause issues in scenarios where the values"true"
or"false"
should be actual strings.I would assume that this a rare case but also wanted to see if anyone else has another opinion?
The text was updated successfully, but these errors were encountered: