String keys for RailDictionary
2 posters
Page 1 of 1
String keys for RailDictionary
Sir Chris,
I wonder if it is possible to allow String as keys for RailDictionary, just like BVETs5? Using strings instead of just numbers will probably enable developers to manage their tracks in a tidier way. Given the amount of track in a normal route, the performance impact should be minor.
Also, I personally think, if string keys are also allowed on FreeObjs, and other things that are so far number-indexed, developers can save a lot of time trying to match the numbers with the objects! Although they can be acheived with preprocessor command $Sub, I still think a built-in support will make things easier.
Thanks!
I wonder if it is possible to allow String as keys for RailDictionary, just like BVETs5? Using strings instead of just numbers will probably enable developers to manage their tracks in a tidier way. Given the amount of track in a normal route, the performance impact should be minor.
Also, I personally think, if string keys are also allowed on FreeObjs, and other things that are so far number-indexed, developers can save a lot of time trying to match the numbers with the objects! Although they can be acheived with preprocessor command $Sub, I still think a built-in support will make things easier.
Thanks!
Re: String keys for RailDictionary
The short answer is dunno
Longer answer-
The current route parser is an absolute minefield. I can see immediate problems with cracks, and a fundamental change like this isn't as easy as it sounds.
After having got the object parsers into shared plugins, one of the next major targets is to do the same for the route parser.
Once this is done, further work on the internals is on the agenda, but I don't want to make any promises on this as it may take somewhat of a while, and may break horribly in the process.....
Longer answer-
The current route parser is an absolute minefield. I can see immediate problems with cracks, and a fundamental change like this isn't as easy as it sounds.
After having got the object parsers into shared plugins, one of the next major targets is to do the same for the route parser.
Once this is done, further work on the internals is on the agenda, but I don't want to make any promises on this as it may take somewhat of a while, and may break horribly in the process.....
Similar topics
» Replacing the 'Security Keys'
» Brake increase/decrease keys not working at all
» I replaced the ATS system with BVEC_ATS to make the R38 from NYCT functioning, but keys do not work at all
» Error Void OpenBveApi.FileSystem.FileSystem.AppendToLogFile(System.String)
» Brake increase/decrease keys not working at all
» I replaced the ATS system with BVEC_ATS to make the R38 from NYCT functioning, but keys do not work at all
» Error Void OpenBveApi.FileSystem.FileSystem.AppendToLogFile(System.String)
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum