Devlog #9 - Expanding The Module Developer API

Before I begin this devlog, I would like to apologize for being inactive over the past week. I have had quite a busy week, and I did not have much of an opportunity to work on PSimUltimate unfortunately.

What I Have Been Working On

I’ve been putting more attention to the module API, modules are the most important part of PSim, and their API should be more advanced than the very basic one that currently exists.

I’ve split the API into 5 different sections:

1. Physics Behavior - callbacks into force, velocity, and positions of particles
2. User Input - adding new keyboard shortcuts, reading mouse positions, reading which keys are being pressed
3. Graphical Behavior - being able to draw stuff on the screen
4. GUI - adding buttons, settings pages, descriptions, and more for specific modules.
5. Other Modules - modules should be able to register dependencies and force certain modules to be either lower or higher than them on the callback order.

I have been hard at work (when I can) on designing and implementing these needs. So far I have made some progress, but there is still much to do and research, and I’m sorry it’s not so juicy for a week’s worth of progress. Either way, thank you for reading, attached is an example of custom buttons that can be registered by modules in the top bar, and please keep following the project for more updates.