Debug in VS2022

[d.healey]

Duplicate your broken project and start removing stuff systematically until the problem goes away

[DanH]

@d-healey I’ve just done that. Which is how I ended up at this script. Unless you mean removing ui objects?

I went through each section one by one switching the ui objects save in preset function to off until nothing was save in preset and still I had the crash. I removed all scripts one by one until I hit this one.

[d.healey]

@DanH If you comment out the laf function does it work?

[DanH]

@d-healey It only works if the whole script above is commented out. If either part is there then it crashes.

It should also be said that this was apparently working fine in the previous edition of the software, created on a commit from last April. The script is identical.

[d.healey]

@DanH I have no idea then, I'm not familiar with the macro panel.

[DanH]

@d-healey ok thanks for the help anyways!

[ustk]

@DanH is that not weird to re-assign the area object?

[d.healey]

@ustk I hadn't noticed that. I usually make a copy with var a = obj.area but since obj.area is an array a is probably just a reference and it hasn't caused me any issues, so I think that it should be fine.

[Adam_G]

@DanH hey there did you ever find any more information about this? im having the same issue in one of my projects and i think its related.

[DanH]

@Adam_G crikey, I can't remember. I think I was just trying to debug for the hell of it and found some things that were flagged up but ultimately it worked out fine...

[Adam_G]

@DanH you mentioned presets that had macro controls in them were causing access violations. did you resolve that?