Ubuntu See more details. See issue details. What will happen in this combination is that the Swing EDT hangs. The only solution is to use native menus in this specific combination; which is automatically handled during SystemTray initialization. The library will auto-switch to a native menu in this situation. Sorry, something went wrong.
Also, would you consider an AWT wrapper addition as optional parameter? If so, I think we can go live with this 3. The windows icon fix alone is reason to implement it. We're currently integrating version 2. For adding menu entries? I'm a little confused. As for using ActionListeners, yea - that could probably happen.
How would you imagine it happening? Just adding a new Menu Entry, but passing it an ActionListener instead? This maps mneumonics and recurses through submenus. Thus, someone who wants native menus on Mac can have them without fragmenting the codebase. Yea, I can probably do something like that. We're working to integrate 2.
This way the listener code won't have to be fragmented. It would truly be a one-size-fits-all solution. From what I understand AppIndicator has its own caveats listeners are bound to a string value but we'll be wrapping all of this anyway probably HashMap the strings and throw exception if a duplicate exists. The swing objects are pretty inexpensive to construct so it would allow GUI developers to code the way they're used to while allowing the library to to the heavy lifting so to speak.
I'll go about adding that functionality as soon as I get some bugs worked out. It does work flawlessly with UbuntuGnome though. Now to figure out what's going on It can help to find the complete stack trace of lib on our systems. Just as a note, there have been some slight API changes, I think for the better. The changes for the most part have all been to simpler method names, IE: a change from SystemTray. It's not a huge difference, but makes the calls less verbose.
I suspect it might be a threading issue -- or, as I've read online, JavaFX on a Mac can only run on physical hardware there are problems with it running in a VM.
Was this meant to mirror the Java API? I have both VM as well as physical hardware to test on. VMs are Physical: We use the classic-style system tray through the AWT wrapper, which I would like to collaborate with you on leveraging a more comprehensive wrapper for such as adding, removing, disabling items. I can likely do byte-code injection to make the tray-icon respond to any click with the mouse.
The screen-shot you provided for what the "default" tray looks like on OSX is pretty compelling. If I provide an IntelliJ project, would you be able to step debug through it to see where it breaks?
Would it help to track these as separate issues? The backtraces could start to fill up this meta-issue. We'll need a bit of hand-holding in regards to which components to test. The fact that you offer multiple testing JARs suggests the main Note also, the product we are implementing with has a service contract with Oracle, if that helps.
However, there is an API change from 2. My system info: Arch amd64 4. I can re-run the test with other WMs if that helps. Are they built upon the source version in the project. Of note, with the native-popups, there are some subtle differences in what each platform supports icons in the menu, text styling in the menu, etc. The preferred popup is swing via get , and getNative is provided for those that want to use native menus.
I think I got the other issues fixed in my repo, though I would suggest implementing the fixes yourself. All that remains now is getting checkbox to start working. I also tested get and it works great, the only issue is that first click, it looks like the popdown covers the cursor and steals the focus.
On a side note, this issue is massive. It may be time to close it and open a compatibility matrix issue with a guide on how to test it on a new os, and open the individual problems as issues that give reference to the matrix issue post that posed them. When the new matrix is created, I have some recommendations:. After the installation of libappindicator1, JavaFX will work as expected.
Because if you want more testing results, your compatibility matrix will help drive it. Finally, I'd really like to see a quick check-out-and-build process. I think you'll have many more pull requests once we can all easily hack against the codebase instead of burdening you with building a Jar each time. Release Candidate jars are on my server, and it should pass all OS combinations in the Compatibility Matrix.
The native menus look amazing. I'm really looking forward to the final release so I can use your library in production. Thanks for all the effort you put into this. I notice a significant flicker when a submenu pops-up. Native submenus don't seem to draw this artifact. I'm not sure if you've noticed this on any other platforms. I'll investigate further. Additionally, the artifact you see is because ElementaryOS changed the threading model for GUI event dispatch beats me why..
The work-around is to force native menus and emit a warning -- which is what happens for 0. Please let me know if you'd prefer this tracked in a separate bug report. The error i'm getting in the gnome-shell logs is tray.
Perhaps we should probably put a note about it in the compat chart. I have elementaryOS 0. Skip to content. Star New issue. Jump to bottom. Milestone 3. Copy link. SystemTray - Error setting tray icon size to: 40 javassist. NotFoundException: sun. WSystemTrayPeer at javassist. SystemTray - Successfully loaded SystemTray - Tooltips are not consistent across all platforms and tray types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Linked pull requests.
0コメント