AOZ Studio V1 (TBD bugs clean/-> V2)

Issues with the debugger.
1) If using an actor with background scrolling left (see picture (grid with scrolling actor backgrounds), the picture scrolls and is maintained inside the preview box, but the grid continues on and outside of the boundries.
..
2) Only really works correctly on the default 1920x1080, It is not resetting the display width and height if custom, when toggling views in the debugger in other custom sizes. Here below you can see what happends with another custom size...
screenshot a) Default 960,600 ok.
.
Next the debugger large preview..
screenshot b) Large preview running in debugger ok.
screenshot c) Now we have clicking debugger icon, to get it back to full screen preview. No good.
Should be like a.png above, but ends up now like, c.png (All squished up vertically).
screenshot d) Now when click debugger icon again, it comes back to debugger windows, but then
from now on the preview is permanently stuck with the wrong size not b.png again.
.
Again other applications don't do this that only stick to 1920x1080. (They are ok).
..
Here is a stock one below. (1920x1080) a screenshot, no modify display width/height.
Then click debugger button, screenshot next. (1920x1080) b screenshot.
Then now back to normal clicking debugger button it again. (1920x1080) c screenshot Works correctly.
3)The scrollbars in the windows, do not let you click+hold mouse down and drag.
You have to currently try and click under or above each scrollbar pot to make them move up or down.
Also..if you click to the right of the program listing scrollbar (the one across the bottom) you can't get back to the left unless you click in the listing and hold left cursor for ages until it scrolls one character at a time.
This effects the (Source code/Variables & also the Stack window).
..
4)At times, when you're doing the STEP mode, it doesn't step into the other section of code. It does un-highlight it was on, but you don't see the current one. If you step again, the cursor will come back, highlighting the next line.
..
5) Can we get the the debugger be able to follow the code on an include file as well as the main code, this would be good.?
6) Could we make it so the debugger will follow the source code when running in "Slow motion" mode?... or at least make it an option?
..
7) The debugger help windows, eh well this is not complete in the debugger at all. (See debuggerhelp screenshot).
Screenshots missing and also main doc linking button currently not implemented. Also debugger usage/insts etc is not actually in the new help system.