If the following change sounds wrong to you, reply soon and I might be convinced not to check it in.
I want to create a new initializer class, that I'd prefer to name ParmInitializer, and I think the existing ParmInitializer class is an unecessary choice, because the better documented PickInitializer class can do everything ParmInitializer was ever used for (as well as things ParmInitializer can't do).
So:
1) I will edit protocols.ini to replace every use of ParmInitializer with an equivalent use of PickInitializer.
2) I will replace ParmInitializer with a new similar class which does things that I think aren't possible with existing initializer classes.
3) I will edit protocols.ini to use the new ParmInitializer class for protocols that I think need it.
This plan assumes that everyone other than the RM gurus get RM updates as a full package, so they could never get a new .jar file with an old .ini file.
RM gurus will need to make sure they get the .java change described in (2) no earlier than they get .ini change described in (1). I will do the CVS update in the correct sequence.
RemoteMaster change in progress
Moderator: Moderators
problem with HexFormat
I sent, via an email address that might or might not be correct, a question about a problem in ManualSettingsDialog.java because HexFormat is undefined. I'm asking here as well in case the email fails or someone other than Greg knows the answer.
Edit: Greg answered by email, but I'm on the wrong computer now to use that answer. I'm sure it will help later.
Edit: Greg answered by email, but I'm on the wrong computer now to use that answer. I'm sure it will help later.