Organizing the button layout in the event table

[beanoccio]

A change to the event area table is planned for Artisan 3.2.1. It took a lot of effort to recreate the old layout. A lot of trial and error was necessary.

The event button table is very effective, but it's always been very difficult to create a defined layout. The new change doesn't improve things. It takes about an hour to get the layout, which you painstakingly created months and years ago, back to the same arrangement as before. (How many people use Artisan? > 40,000)

I recommend two additional row types:

on = visible (still exist)
off = hide (still exist)

• New button row (line break)
• Spacing (horizontal spacing between two buttons)

This way, there's no longer any need to count invisible and visible buttons.

[roasterdave]

You must have hidden buttons at the top of your Events Buttons table, before the first visible button. If that is the case, to keep the same layout after this change add an equivalent number of hidden buttons at the end of the first row. For example, if there are five hidden buttons at the top of the table, add five hidden buttons after the last visible button in the first row. These added hidden buttons need no action or labels. Only the first row needs to be adjusted. Your original layout will be retained.

If the first button in the Events Buttons is visible this feature change is transparent and does not affect the buttons layout.

This change allows using hidden buttons at the top of the Events Buttons table to hold actions referenced by alarms and other buttons. By locating them at the top of the table their reference numbers (row numbers) will be kept static when other changes are being made to the button table. Visible buttons are further down in the table and their order can change at will without affecting the references to the hidden action buttons.

[beanoccio]

I tried some characters for comments. I didn't think of the #. How embarrassing, knowing that Artisan is written in Python. Thanks for the tip!

[MAKOMO]

Well this is documented in the Help text within the Alarms dialog...

[roasterdave]

@beanoccio Today's continuous build works slightly differently from previous continuous builds. Hidden buttons with a Type or Action defined, at the top of the events buttons table, will not be counted in the first row's button count. However, hidden buttons with no Type or Action defined are always counted and can be used as spacers at the start of row 1. I haven't seen your buttons table to know if this behavior will affect your button layout. If it does you may need to move the newly created "spacer" hidden buttons at the end of your first row to the beginning of the row, just after any hidden buttons with a Type or Action defined.

[beanoccio]

Thank you for the advance support! I've downloaded the new Artisan 3.2.1 build (8fd6bb0). Yes, the button layout was changed again.
But I was able to quickly correct the changes to my button layout. Everything is pixel-perfect again, in the desired position and row!

[roasterdave]

Excellent! Glad it was quick and easy.