[zork]

I tested it. It is in fact still really simple to do. This is all you need:
https://github.com/zorker/rothui/blo...rTest/bar1.lua

Currently debating if I want to add it. It helps merging a lot of bars. One does not even need to create a vehicle exit button. One can just reparent the OverrideActionBar.LeaveButton and change its visibility based on the canexitvehicle macro condition.

Ok I did change it. Was super easy to implement:

https://github.com/zorker/rothui/com...85cc2000a2091d

The main part is this macro condition:

"[vehicleui] 1; [possessbar] 2; [overridebar] 3; [shapeshift] 4; [bar:2] 5; [bar:3] 6; [bar:4] 7; [bar:5] 8; [bar:6] 9; [bonusbar:1] 10; [bonusbar:2] 11; [bonusbar:3] 12; [bonusbar:4] 13; 14"

Basically just a number that counts up for each macro condition. I only need it to fire the __onstate-page trigger. In the function we have access to all the functions that the actionbarcontroller has access to aswell.

frame:SetAttribute("_onstate-page", [[
      if HasVehicleActionBar() then
        newstate = GetVehicleBarIndex()
      elseif HasOverrideActionBar() then
        newstate = GetOverrideBarIndex()
      elseif HasTempShapeshiftActionBar() then
        newstate = GetTempShapeshiftBarIndex()
      elseif GetBonusBarOffset() > 0 then
        newstate = GetBonusBarOffset()+6
      else
        newstate = GetActionBarPage()
      end
      for i, button in next, buttons do
        button:SetAttribute("actionpage", newstate);
      end
    ]])

Result: https://github.com/zorker/rothui/blo.../init.lua#L100