Ple-ease, could you also allow for queue-style message handling?

For example, add a "UseQueueSystem" boolean to the interface, and a Queue<string> for messages. If UseQueueSystem is true, then instead of invoking the PB the antenna will simply store the message in the queue. To prevent abuse and overload, the Queue will only hold up to 20 messages, and if the queue overflows, the oldest message will be removed in order to place the new one.



Of course "you can always implement this by yourself in your script", but it will be very nice if we really were given options on how we want to handle the messaging. In certain circumstances, this may be beneficial for performance. Imagine you have a central control station, which controls 10 drones. These drones report their positions and their integrity, so their status can be displayed on an LCD. So, with the Queue option, instead of running the PB on central station 10 times and handling one message at a time (and redraw the LCD 10 times, etc...), the PB could be run only once with a timer, and process 10 messages in single run. This may greatly decrease performance impact if, for example, you are doing an inventory lister script for several stations, which displays a combined readout of ingots, components, etc across your facilities.

Click to expand...