....
1) can the section <ui_model type="EmissivityMaterialSettingsModel" name="emissivityMaterialModel">
<ui_model_item type="SettingItem" label="ID_EMISS_CONCRETE" value="0.95"/>
... be resorted alphabetically buy moving the lines around?
2)can I change the power options timers from
<ui_model type="AutoPowerOffSettingsModel" name="autoPowerOffSettingsModel">
<ui_model_item type="SettingItem" ID="POWER_OFF" label="ID_SETUP_OFF" radio="true"/>
...
to other times, such as 15 min and 60 min by replacing the values/
3) Is the backlight brightness for low/medium/high predefined in hardware? I would like to change the low and medium levels if possible.
4) One more... where is the Flir logo "color" setting? I wouldn't mind trying a very faint image being displayed.
@ 1): just resort them and see what happens - I think they were sorted by alphabet before I messed with them - anyway "never" used
@ 2+3): I find the default values are just fine, but take a look at .power.setting (below) values below (telnet, command rls). You can replace the default settings by a new "model" that changes the wanted value directly - anything with ID_ is a pre-defined placeholder (defined in the language-files) and usually pre-associated with some value(in facet_ui_qml.dll), but the registry most times allows for entry of numeric values - best idea: first test by using rls/rset over telnet.
Define a SettingsValueModel, change the ID to something unique, label it, set min, max and step (better don't allow 0 as it would turn off the backlight), define resource="..power.settings.trueBacklight"
... then add that model-name to a menu entry where you like it - don't add it inside a RADIO list - you can take my humidity settings as example.
Strings:
AUTO_POWER_OFF: ID_SETUP_OFF ID_SETUP_5_MIN ID_SETUP_20_MIN
DISPLAY_INTENSITY: ID_SETUP_LOW ID_SETUP_MEDIUM ID_SETUP_HIGHLow, Medium, High here are direct values inside the registry, which on change sets the true value (see below) - the situation is different with the auto-power-off settings.
.power.settings: (12)
acOffTime 1140 <- would be 19 minutes + 55 sec + 5 sec = 20 minutes
acSysIdleTime 55
acUserIdleTime 5
battOffTime 1140 <-- same here
battSysIdleTime 55
battUserIdleTime 5
dumpActive true <-- write statistics, probably better get turned off in some .rsc.. but might have side-effects
laserAllowed true <-- useless
laserEnable false <-- useless
screenSaverEnable false <-- useless
subjectiveBkl "medium" <-- allowed: ["low" "medium" "high"] .. sets the "trueBacklight" value
trueBacklight 40 <= 40% PWM, this is the value you'd want to fine-tune for better backlight control
@4) this has been discussed with another user already - it's a ressource file manipulation (RCC) - I prefer not having the logo on, as it's no longer a "pure" FLIR ... not to forget that the logo takes away visible image pixels which were hard-earned