Ok, this seems useful enough
I'll try to make the GUI dynamic.
Maybe some sort of "Extended Options" Button - or patch setting, which expands the GUI to show all uncommon features.
Something to discuss:
Does it help, or disturb to implement a partial station copy&paste?
This means:
---
-Only uniform stations will be pasted as intended.
-Non-Uniform stations will produce something more or less unpredictable.
->may split into 2 or more stations
->maybe only partial rebuild
Would result in:
Y is a second station.
The last XXX can't be rebuild, since 2 different stations would touch eachother.
->Non-touching single stations would always result in 2 stations.
---
Or save the effort and just insert the stations afterwards.
(Makes sense if you want to use different newstations anyway.)
This is, how it is now.
Another thing comes to my mind:
Currently the maximum copy size is fixed to 64x64, because I use static arrays.
This seems to be common in openttd - to use arrays, instead of dynamic memory allocation. (e.g.: CustomNames array)
Is there some reason behind this? Or may I just switch to dynamic datastructures?
Pro:
-Unlimited(ram) copysize.
-No Memory usage, if feature is not used.
Con:
-Heap fragmentation. (Don't know if this really is a problem)
-a little more overhead memory usage per copied tile
The command-queue would benfit most from using a dynamic datastructure.
Maybe some developer has some background information on this topic.