V16.0 Beta Feedback - Tab height / can't change theme color opacity & more

General
1

Hello Graeme, thanks for the v16.0 Beta preview.

I quickly had two “issues” with it (on Windows), and wonder if they are already addressed:

  • The tabs became very tall, even when not using the title bar tab mode and after decreasing the font size. Is there a setting to decrease their height back to the original size?
  • Updating my VS2022-like theme, I can no longer pick color opacities in the settings theme color table. Clicking the slider just closes the color popup, and adjusting it with the keyboard does not apply the chosen opacity. Sadly, the 1tm theme files seem to have a proprietary format, and I cannot figure out where to change the opacity in them aswell.

I also have some questions / feature requests:

  • Can the decimal/hex display format be made available for the template results Start and Size columns aswell?
  • The following template code would complain that Variable 'x' has already been declared if there is more than 1 row:
    for (int y = 0; y < rows; ++y)
{
    for (int x = 0; x < cols; ++x)
    {
    I know that modern variable scope is not a thing in templates yet, but is there a chance to at least see x and y becoming scoped to their for-blocks itself, allowing loops and reuse like this?

Thank you for your continued work on this product.

2

Thanks for taking a look at the beta. The tab height has increased on Windows from 24 pixels to 30 pixels because it looks a little better when the tabs are in the title bar. We don’t have an option right now to go back to the thinner tabs but and could add that in, but I’m not sure if we’ll be able to get it in before the full release. The opacity slider should be fixed in beta2 which should go up in a few days, and it is also very easy to add in a decimal/hex option to the start and size columns.

You are correct that having nested for statements like this causes an error and it would be nice if it worked correctly. Scoping for variables has always been tricky in 010 Editor since template variables always exist even outside { } blocks. We made local variables have the same scoping rules as template variables but perhaps we should have switched to ANSI C style scoping. We could still make this change at some point but it may break a lot of templates and scripts. In this case, a work-around could be that if you declare ‘int x’ inside a for loop and the x variable already exists, then it is overwritten. That would allow the nesting to work and we’ll take a look at this more. Cheers!

Graeme
SweetScape Software