You best bet is to run it in eclipse in debug mode. Put a breakpoint right before the dialog is created and step though to see if there are any errors. Sometimes you can get errors in the static initialization of classes. By stepping through you should see where any errors are.
Paul Sunburned Surveyor wrote: > I've got a quick question about internationalization. I've completed > the internationalization of the Super Select Tool and was testing out > the latest build. One of my dialog boxes for the tool (which had > worked previously) now will not open. > > If I have a mistake in my I18N work (for example: a mispelled > key/value pair) would this cause the dialog not to open? Or would this > generate an exception instead? > > Any suggestions on a quick way to track down a misspelled key? (I mean > a key in the source code that doesn't match a key in the resource > file.) > > I'm a little new at this I18N stuff, so I appreciate any suggestions. > > Thanks, > > The Sunburned Surveyor > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
