java 中的干扰 Keylistener
我有一个 JXTree，我想以这种方式添加搜索：
当用户键入时，模型返回树的匹配元素，并在树视图中选择集合中的第一个元素。 问题是，默认情况下 JXTree 有另一个键侦听器，它选择以当前键入的字母开头的元素。
有时，本机侦听器最后触发会导致结果错误。可以采取什么措施来防止这种行为？我不想删除固有的侦听器，因为它具有基于箭头的导航...（我必须重新实现。） 我已经读过这个： Is the order in which KeyListeners 将被称为有保证？，但我不认为我可以毫不费力地创建建议的侦听器包装器，因为 BasicTreeUI 的 Handler 类是私有的。
I have a JXTree and I'd like to add searching to it this way:
As the user types, the model returns the matching elements of the tree and selects the first one of the set in the tree's view.
The problem is, that by default the JXTree has an other keylistener, that selects an element starting with the currently typed letter.
Sometimes the native listener fires last making the outcome wrong. What can be done to prevent this behavior? I don't want to remove the inherent listener because it has arrow based navigation... (Which I have to reimplement.)
I've already read this: Is the order in which KeyListeners will be called guaranteed?, but I don't think that I can create the proposed listener wrapper without great effort, since BasicTreeUI's Handler class is private.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这不是 JXTree 的功能，而是 JTree 的功能。重写 JTree#getNextMatch() 以始终返回 null 应禁用按键时的 JTree 选择。
That's not a feature of JXTree but JTree. Overriding JTree#getNextMatch() to always return null should disable the JTree selection on key press.