Win32 exception when using readout mode on image

[Nocturnal]

Hi,

here's approximately what I did:

- update PI Win x64 with latest modules
- load image
- automatic STF
- place DBE samples
- do subtraction without replacing target image
- do subtraction, replacing target image
- save image (luckily!)
- close DBE process
- reapply automatic STF
- click and hold in image to examine stars
- error dialog as shown pops up, after dismissing I get a new one
- readout popup appears on top of every window, even visible now with Firefox full screen to type this message

Haven't tried to repeat this yet. Will have to kill PI.

[Nocturnal]

Oh boy, this is pretty bad. PI throws up this error every time I click on an image even after a fresh PI start and image load. Once PI gets in this state all I have to do is move the cursor on the image (no need to click) to throw up the error. Restarting PI is the only option. I don't see how a few new modules can cause this but I'll restore to a default PI install.

[Juan Conejero]

Hi Sander,

This typically happens because a module is receiving sample readout notifications and has a bug in its reimplementations of the notification handler routines:

void ProcessInterface::BeginReadout( const View& v )
void ProcessInterface::UpdateReadout( const View& v, const DPoint& p, double R, double G, double B, double A )
void ProcessInterface::EndReadout( const View& v )

To check if this is the problem, please do the following:

- Click the small blue triangular icon at the bottom of PI's main window (Readout Options)
- Select Readout Data and disable the Broadcast Readouts option.

If now the bug is gone, then you know this is the reason. Ask Carlos what he's doing 

[Nocturnal]

I'll try that later. I'm in the middle of processing an image and don't want to crash PI now.

[Carlos Milovic]

Hi Sander

I'm 90% sure that this is my fault Do you have ColorRange installed? It has the menctioned bug, that I have not catched yet. The workaround is opening the ColorRange interface once (you may close it again), and everything works again (for the current session).

[Nocturnal]

Thanks Carlos

[sleshin]

I also experienced this error after installing all of Carlos' modules. Didn't try to figure out which one might be responsible, just uninstalled all of them and all was well again. Thought I'd wait for the fix before reinstalling.

Steve