Sponsored day report

report

Focus was on passing on the hidlib context to all actions, making the action code more reentrant. This is essential long term, for two reasons:

• for other ringdove apps: librnd (including hidlib) code can not depend on a global variable such as PCB, because that won't exist in another application, still it needs access UI states thta is normally stored with the board (e.g. grid settings may be different from board to board). With proper tracking of the hildib parameter, more plugins become available for the hidlib.
• long term, very far in the future, if every corner of the code loses the global var PCB dependency, pcb-rnd may get an optional multi-board support (e.g. with tabs). The sch editor will need this from early on so the GUI will need to be prepared anyway.