It might be useful for Authors to have a default API for placing their root-elements on the container of the Blish Overlay.
It should support things like anchoring:
Horizontal anchor
Specify where to anchor elements horizontall (left canvas edge, middle of the canvas , right canvas edge)
Vertical anchor
Specify where to anchor elements vertically (top canvas edge, middle of the canvas , bottom canvas edge)
Anchor Offset
This would specify the offset of the element from the anchor point (relative, absolute value or percentage of canvas size)
Pivot Offset
Allow the element to move its origin / pivot point, maybe this should be a relative placement option like x=1.0 (meaning 100%) would move the pivot to the right edge of the element
Having those options would allow authors to offer options to users where they want to place elements on the canvas. I.e. anchor an element to the bottom right corner of the screen and move it 300 pixels to the left. With this the element could be pinned next to the mini map, even when the game window size changes or the player switches between full screen and window mode.
Real World use case example:
I am playing on a 32:9 monitor for normal gameplay, but when I'm following some guides I might have the browser window on one half of the screen and the game on the other half, so the game has then only 50 % of screen width, all the placed Overlay UI in Blish does not adjust to these changes, throwing the elements off the screen.
My current workaround:
I wrote myself a script, that kills Blish, will go through all the Blish options and adjusting the position settings in the config JSONs, and then starting up BlishHUD again.
It might be useful for Authors to have a default API for placing their root-elements on the container of the Blish Overlay.
It should support things like anchoring:
Having those options would allow authors to offer options to users where they want to place elements on the canvas. I.e. anchor an element to the bottom right corner of the screen and move it 300 pixels to the left. With this the element could be pinned next to the mini map, even when the game window size changes or the player switches between full screen and window mode.
Real World use case example: I am playing on a 32:9 monitor for normal gameplay, but when I'm following some guides I might have the browser window on one half of the screen and the game on the other half, so the game has then only 50 % of screen width, all the placed Overlay UI in Blish does not adjust to these changes, throwing the elements off the screen.
My current workaround: I wrote myself a script, that kills Blish, will go through all the Blish options and adjusting the position settings in the config JSONs, and then starting up BlishHUD again.