uri_ba Posted July 8, 2021 Posted July 8, 2021 (edited) Hi all, Other then finding the max idx in world.getMarkPanels() is there a cleaner way to get the next idx? As if there is no marker, the output is empty and you have to guess the next idx and hope you got it right (or no marker for you) Thanks! Update - another interesting tid bit. Whichever method i will implement will break MOOSE and alike. I've looked at their implementation, it's based on a static running id counter. For that matter, even if i add a manual marker with moosearkers running it might "break" moose (it'll skip a few markers till it gets a proper number. So we must be able to get a current/next id from the base DCS classes to be able to play together nicely. Something like world.getMarkID() which will give you a ready to use ID number and handle conflicts. Edited July 8, 2021 by uri_ba Creator of Hound ELINT script My pit building blog Few DIY projects on Github: DIY Cougar throttle Standalone USB controller | DIY FCC3 Standalone USB Controller
uri_ba Posted July 10, 2021 Author Posted July 10, 2021 I'm learning new things 1. IDX does not have to be consecutive, just unique. 2. it seems that the user added markpoints are in the 251,000,000+ region. so unless you think you are going to add a few millions, it's safe to start at a lower number. try not to start at 1 (as MOOSE starts there), and give yourself some headroom. I've started at 100k, you can start at 1M. and if more frameworks would join, we can do 1M, 2M, 3M etc.. I don't thing anyone will add more then a million markers over the course of a mission. 1 Creator of Hound ELINT script My pit building blog Few DIY projects on Github: DIY Cougar throttle Standalone USB controller | DIY FCC3 Standalone USB Controller
Recommended Posts