SubframeSelector halt!!

[matelunga]

I just installed the new version 1092!!


PixInsight Core 01.08.01.1092 Ripley (x64)
Copyright (C) 2003-2014 Pleiades Astrophoto
----------------------------------------------------------------------
Welcome to PixInsight. Started 2014-abr-26 17:05:42 J2456774.21229 UTC

* Parallel processing enabled: Using 8 logical processors.
* Thread CPU affinity control enabled.
* PSM AutoSave enabled. Auto-save period: 30 seconds.

run --execute-mode=auto "C:/Program Files/PixInsight/src/scripts/mschuster/SubframeSelector/SubframeSelector.js"

Processing script file: C:/Program Files/PixInsight/src/scripts/mschuster/SubframeSelector/SubframeSelector.js
*** Error [000]: C:/Program Files/PixInsight/src/scripts/mschuster/SubframeSelector/SubframeSelector.js, line 172: Error: TreeBoxNode.Set(): invalid argument type: boolean value expected.


any idea!!
best regards
Pablo

[mschuster]

Hi Pablo,

Sorry for the trouble. Please try the following:

- Exit all PixInsight instances.
- From the Win OS Start Menu, choose All Programs > Pixinsight Platform > Reset PixInsight Settings.
- Relaunch PixInsight and try SubframeSelector again.

If the problem persists, please try Pixinsight Platform > Uninstall PixInsight first and then reinstall 1092 again.

The script sometimes encounters problems with saved parameters. Clearing them as above often solves the problem.

Thanks,
Mike

[matelunga]

Thanks Mike, it worked perfectly 

[bitli]

It may be stating the obvious, but you should then check and probably restore your global settings (Edit/ColorManagementSetup, default RGBWorkingspace, ...) if they did not have the default value.
-- bitli

[mschuster]

Bitli,
When reading Parameters/Settings and assigning to process instances try/catch probably should be used for corrupted value handling and recovery. Also checksums on saved values would be a good idea. Data gets corrupted occasionally.
Mike