Inline action bar command order and number

Are there any plans to provide configuration of the number of icons and their order in the inline action bar?

I can see that there's a default setting of 5 icons and that the order is determined by the module load order and the enabled response. So while this could be changed in the csui bundles, it would obviously be removed by patching (and probably take us out of support). Is there another configuration option for this somewhere I'm missing?

Find more posts tagged with

Comments

Ugis

Hi,

I saw in one example (samples\commands\open.brava\...actions.js) that OT was using sequence:X parameter with comment "Less than 10 takes priority over the buikt-in command", but when I try to use this for my custom command, it doesn't work. My command is always displayed as last one in the list.

I'm too looking for possibility to boost my custom command to preffereable sequence 1-5 so that it would be visible also as icon and not under "more" menu.

Does anybody know if that is possible to implement? (and not modifying core files).

Thanks,

Ugis

Uldis

There should be someone who knows this - Is there a way to add order (e.g. 2nd) for custom inline commands?

Ferdinand Prantl

I'm afraid, that specifying the position of a button on the toolbar is impossible today. The sequence number is a concept used often for extension ordering, but not for toolbars and context menus.

Before 16.2.5 it was possible to use a workaround with groups. If you specified a group, your button would be appended at the end of the group. For example, specifying the group "info" in your button definition would put it right after the Properties button, which means the 2nd place. (The group "info" is the first one and there is only the Properties button there.)

However, promoted actions introduced in 16.2.5 effectively disabled positioning of custom buttons to the predefined groups. Only commands permitted by promoted actions implemented in VS core can appear there. All custom commands can be permitted only by non-promoted actions. And as such, all custom buttons are appended to the end of the toolbar.

You could file a feature request for this. There was at least one issue created about it (LPAD-63886), but its scope is too big. I cannot find any issue about just implementing the functionality in the framework, so that at least the developers could specify the default position of their buttons.