DC / DIB / Undrawable Canvas errors [MAJOR BUG] [EDITOR]

[Wafflem]

Editor: V10.12.12-B

I have no idea how exactly to reproduce this behavior, but sometimes when I hold down to look for a terrain/object in their respective menus, I get some really nasty errors and the editor crashes:

Can't create compatible DC.
Can't allocate the DIB handle.
Canvas does not allow drawing.

The third one is the worst of all as a lot of the dialog boxes of this error pop up. I've attached pictures of all three errors.

[GigaLem]

This did happen to me before when I scrolled too fast through the terrain menu.
My suggestion to Namida would be to make that when you select a tileset from the drop down menu it'll be forced to let you scroll through the tileset's pieces until you select through the drop down menu again.

[IchoTolot]

Nepster and I can confirm this bug.

We've discussed it in IRC and found out this happens on dragging, (mousewheel) scrolling and clicking the arrow buttons for a longer time period. So all scrollbar actions are bugged to an extent.

This bug did not occur to me until now as I pretty much only drag the bar and that's very quick ---> no longer search. So that could be a ~ workaround until it's fixed.

[Nepster]

There seems to be some bug with the new scroll bar. With the current version, there seems to be no way to safely handle it: Arrow keys, moving the mouse wheel and dragging the scroll bar all trigger this bug.

I attached the editor version V10.12.11 that I had still lying around, if anyone needs to go back to a properly working editor.

[namida]

I did encounter this during testing, but thought I had fixed it before release. Seems not. Will investigate further, and if I can't have a fix by later today, I'll put the old version back up for download.

I believe (though do not have outright confirmation) that the bug is in fact related to the drawing backgrounds and 2x zooming of pieces change; not the scrollbar fixes.

[namida]

My guess was correct. I've uploaded a V10.12.12-C hotfix that should fix this issue. (This issue only affects V10.12.12 and V10.12.12-B, with the former being more prone to it than the latter. If you're still on V10.12.11, this update is not critical.) At least, I neither got errors nor (via task manager) saw NL Editor's memory usage spiralling out of control with this update.

[namida]

Has anyone had this issue on V10.12.12-C? If not, I'm going to close this topic, since it would appear to be fixed now.

[namida]

I'll take that as a no. If anyone does get such errors, please create a new topic to report them.