Support Board
Date/Time: Sun, 15 Feb 2026 09:22:04 +0000
Post From: Input DisplayOrder breaks with non-contiguous inputs
| [2025-12-31 18:09:27] |
| User719512 - Posts: 417 |
|
Thank you Sierra for the confirmation. Fully respect your decision and explanation for the design. For other readers of this thread who might stumble upon this thread: I did find a workaround (which may or may not be Sierra-approved, nor guaranteed to work in the future) -- Caveat emptor. I see no (measurable^^) side effects in my studies by adding the following in SetDefaults before the study's normal input default settings // workaround for Sierra display ordering quirk for (int index = 0; index < SC_INPUTS_AVAILABLE; ++index) { sc.Input[index].SetInt(0); } ^^NOTE: I am sure there is some impact from this (nothing is ever free), extra allocations, class constructors, or something. Not here to pick that apart or turn this into a performance thread/etc. This is simply making the study use all available inputs and the costs that come with that, and like normal, inputs hidden from users do not set the Name field. So, I would expect a study configured like this to have perf of a study using all 128 inputs which may or may not be slower than a study using 4 inputs. |