A better way than using system properties?

Jump to navigation Jump to search

A better way than using system properties?

The current mechanism I'm using to permit RoboTweaker to set tweak values on a robot is to have the robot load them from system properties. This works fine, but has a fundamental problem: it makes it so that I cannot easily speed things up by running multiple battles simultaneously. (I could theoretically wait for the first round to complete, then assume that all classes using these values have been loaded, then go ahead and fire up the next one.) Writing a properties file in the robot's data directory to be read by the robot runs up against the same issue. What would be good would be if I could find a way to set these values that would be scoped to the RobocodeEngine instance in question. Any ideas?

RobertWalker (talk)‎06:18, 13 May 2016

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:RoboTweaker/A better way than using system properties?/reply.

 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:RoboTweaker/A_better_way_than_using_system_properties%3F#A_better_way_than_using_system_properties.3F_4932"