Hi Li,
I'm afraid pluggable editors only work for 'binary' editors, not
for string editors. The original reason was that checking for a
pluggable editor is an expensive operation, so we didn't allow
pluggable string editors as it might slow things down. I don't think
this is so important now, so we should change this in the future.
However at the moment, the only way to do what you want to do
would be to build your own version of JXplorer, and add the check
directly to com.ca.directory.jxplorer.viewer.AttributeValueCellEditor
in the method getTableCellEditorComponent() - there's a list of
editors that are triggered on different syntaxes, you could slot
yours in there.
hope this helps,
Chris
On 03/08/2005, at 10:20 AM, Li Yang wrote:
Hi, Chris:
I'm trying out Pluggable Attribute Editor by implementing
AbstractStringEditor. What I have is orclACIEditor.class which
extends JDialog implements AbstractStringEditor, but I don't see
anyware it is trying to load this pluggable attribute. When I open
JXplorer and click 'orclACI' attribute value in the default table
editor cell, it still pops up the LargeStringEditor. By examing the
code, the only place where is tring to load pluggable attribute is
in AttributeValueCellEditor.startBinaryEditor(), but it is only
tring to load binary editor. Can you please let me know what I am
missing to make my Pluggable attribute editor(attribute orclACI is
type String) work?
Thanks,
Li
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Jxplorer-devel mailing list
Jxplorer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jxplorer-devel
