BUG: designer force closure corrupts settings

[TestBoy]

Having encountered this in my own apps I bet it's the same issue here.

Micorosft in it's infinite wisdom decided to do updates when I left the designer open during the night.
When I tried to run the designer this morning it would run and appear in the taskbar but I could not get it to come forward.
It's as if the window was in an XY location that is invalid.

When I deleted Stimulsoft.Report.settings in AppData\Local\Stimulsoft this fixed the issue.

I saved copies of the bad config files if anyone would like to review them.
I saw nothing obvious in the file but I willing to bet that the forced closure caused a bad value to be written.
File not attached because there is some private information stored there in plain text.

[Lech Kulikowski]

Hello,

Could you send us a step by step guide how to reproduce the issue?

Thank you.

[TestBoy]

Easy. Kill the app.
Doesn't happen all the time. I tried to kill it around 30 times and it didn't happen.

What I can send you is the corrupted settings and you can use that to see what bad data was written and ignore it if it happens.
This is the second time I have had it happen, which is what prompted the post.

[Lech Kulikowski]

Hello,

Please send us a settings files for analysis on support@stimulsoft.com

Thank you.

[TestBoy]

Sent.

Thanks for taking a look.

[Andrew]

Hello,

You are welcome! Waiting for your email.