The initAction has been a constant source bugs. I have fixed the
connections a large number of times. At least five and I am sick of
it. The "normal" way provides better integration with eclipse, good
warnings in the logs and usually compile time checking because you are
referencing a field not using a magic string.
That is why I have deprecated the initAction method. Also the Cleanup
functionality of eclipse doesn't recognize it so it kills the entries.
Jesse
On 4-Sep-08, at 9:52 PM, Jody Garnett wrote:
Found the problem - the contract for Messages.initAction had been
changed in the net.refractions.udig.ui plugin - it no longer would
search the properties files (only the entries that had been loaded
into fields in the Messages class would be checked). As such (even
through the translations have been preserved in the
messages.properties files) they were not being picked up.
Jesse has deprecated the initAction method; but the @deprecate
method did not explain why ... I personally find the initAction
method to be useful; but it is looking like the automation of the
ExternalizeStrings method is playing against me...
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
