Another BinaryRivers.BackyardEOS.Start has stopped working

[JimmyE1971]

I just upgraded from Ver. 2.08 of BYE to the newest 3.1.14 Premium Edition.  Being excited of all the new features compared to my older release I started exploring.  After connecting the camera, but before taking an image, I noticed the screen stretch box in the histogram center and grabbed one of the curve points and moved it.  This immediately crashed BYE giving the above error.  I restarted BYE, connected the camera, and took an image and tried moving the screen stretch function around again and it worked fine.  I know that you wouldn't ever have any reason to mess with screen stretch unless you had taken an image, but it is just a bug I happened upon.  I tried it several more times and got the same error each time.  Thanks!

 

Jimmy Eubanks

[admin]

So you played with screen stretch before taking a single image and it crashed?  After you've taken at least image it works fine?  If this is the case it should an easy fix.

Regards,

[JimmyE1971]

That's correct!  Not a big deal... I probably would have never even found this, but I was like a kid in a candy store after moving to a newer Premium version, and started pushing every button I saw just to see what they did.

 

Jimmy

[admin]

okay, thanks.

[JTWaters]

This has happened to me several times while taking images.  BYE crashes or locks-up while downloading images from my 6D / T3i and I need to restart it.  I consider this a bug...  If I don't stretch an already downloaded image BYE is stable.  Its more prone to lock-up if the image is downloading and you stretch an existing image at the same time.   If I recall correctly I was told that this was a DirectX problem. 

IMHO BYE stability is iffy when stretching already downloaded images.

 

[admin]

3 hours ago, JTWaters said:

Its more prone to lock-up if the image is downloading and you stretch an existing image at the same time.  

 

This is actually a good hint.  Thank you.  Stretching involves manipulation the in-memory image that is also referenced by the Windows picture box control.  A downloaded image also updates the Windows picture box control... I wonder if this is related; updating the picture box control must occurs in the UI Thread which theoretically already assures that only one event is updating the picture box control but the screen stretch is referencing the old image and perhaps (maybe) this is where the bug is.  This is going to take some time to look at.  These things are complicated sometimes.

Regards,