Re: [xPG] passphrase again and again

[Frank L. <fra...@we...>]

Hi, folks,

sorry for the delay, i've got a "too many open Baustellen"-Error. :)
 
After some little changes i've now checked in rubens passphrase-input
classes .

In general it isn't a good idea to make a swing-component (JCheckBox)
static. 
Especially for sharing a state (or data) between several instances of a
Dialog.
This is now fixed. 
The Engine class (@see getOptions) is the right place for storing all
states(data) 
of xpg so adding an Option "hide passphrase typing" to it was a better
idea IMHO.
So the "hide passphrase typing"-Option its also in the preferences panel
automatically. 

The passPhrase-input reads the initial state via the mainFrame from the
engine.
Selection/ deselection of the checkbox sets the state in the engine.

There is now an additional xpg.util.CharArray class. 
It deletes the internal char array for security reasons before setting a
new one 
and cleans itself before it goes to the orcus of gc. :)
A static clear method can ovwerwrite the contents of a primitive char[]
-
this is now used by the engine and PassPhraseInput.

The MainMenu has got an Entry [edit]->[Enter Passphrase] for testing
purposes.

As far as i can see these are all changes.
Must prepare for the bread-and-butter-stuff in the morning and go to
bed.

Nice Work done, Ruben.

Regards, Frank