I'm using a JavaFX calendar widget from JFoenix but for a few days, I get an extraordinary display output. There are strange symbols shown, but I get this error only on my system. When sending the jar to other PCs it works fine.
Maybe someone has an idea whats wrong or has seen a similar problem.
Related
I am having problems using the Ikonli icon packs. I am creating FontIcon objects and then using those to set the graphics on buttons. Icons taken from the FontAwesome5 pack work great. Icons taken from the Material2 pack seem to shift somehow - for example, I try to get mdal-6_ft_apart but what actually gets displayed is mdal-loyalty. And no matter which Icon I load from MaterialDesign2, all I see is an empty box.
I'm running this through Eclipse, and everything looks fine when stepping through with the debugger. This is the value of the button graphic:
ObjectProperty [bean: mdal-6_ft_apart:15:0xffffffff, name: iconCode, value: MDAL_6_FT_APART]
and yet, on the screen, it's something completely different.
This is a Maven project using OpenJDK 16 and JavaFX 16. I've tried loading just a single icon pack instead of all 3, but no difference. Also, there are never any errors retrieving the icons. The ServiceProviders are all found, and the icons are available.
I made a small Hello World program and everything runs fine, so it's definitely an issue with my program and not the library. But I have no idea what the problem is, and I've been staring at this for almost 2 hours. Has anyone come across this before? I'd appreciate any help, because I'm out of ideas.
Answering this myself in case it saves someone else some time. I was installing the Ikonli library in order to replace the FontAwesomeFX library that is no longer available. I had gotten partway through replacing the icons when I ran the app in order to check the progress, and that's when I saw the errors.
The problem turned out to be an interference between the two libraries - FontAwesomeFX was throwing of Ikonli. The icon shift didn't actually occur until the code displayed a FontAwesomeFX icon, which made it seem a little random depending on the order I would open the dialogs when testing. I'm assuming an issue with the Service Handlers, though I'm not positive because I stopped troubleshooting once I realized the problem and just finished the replacement.
Once I stopped displaying FontAwesomeFX icons and the dependency was removed, Ikonli worked fine.
Or is it just me. My own project using tracked hands was working fine yesterday, then today the hands stopped working. After reversing changes since then and still failing, I rechecked one example that was working correctly on Jan. 20: https://aframe.io/aframe/examples/showcase/hand-tracking/ - now, it is not showing hands, or allowing the controls to be used. The hands do show outside of VR when the controller is set down or inside VR when the Menu is invoked. On my device, Hand tracking is on, and the experimental 'WebXR experiences with hand and joint tracking', in chrome://flags, is enabled, both of which I believe are required and were enabled when this was working previously. Turned everything off and on several times, removed batteries, re-paired controllers and did a factory reset of the headset, all per instructions from Oculus support - to no avail. They said they will contact me after asking for invoice info. However it would be good to know if this is some other issue. Can anyone confirm that the above example is, or is not, failing in Quest 2, or is there some other update or change that might be affecting this?
Same for me on Quest 1.
The Three.js examples with Handtracking are working.
Try https://threejs.org/examples/?q=webxr#webxr_vr_handinput_cubes
I recognized that the oculus browser now says "...wants to enter with handtracking" So something changed in the oculus browser that has to be updated in the jslibraries.
But that will change again with chromium 88
I am on oculus browser 13.4.0.3.15 with chromium 87.0.4280
There must have been one cause I had the same problem.
Found this seemingly related fix in the A-Frame code, mostly bone name changes.
And that's what helped me.
<script src="https://aframe.io/releases/1.2.0/aframe.min.js"></script>
I was calling for a previous version of the framework.
I am facing a strange problem: When running my application everything works fine, the code compiles, the debugger shows that everything is in order but stages different to the primary stage do not show their continent, they appear just empty white.
I cannot provide a reproducible code sample because it works on my other system just OK.
So my question is: What could cause the stages not to display their content?
I am using JavaFX 11 with ZuluFX 11.
UPDATE: I just tried to run version which was built on a system where the displaying works and I have the same effect: Empty windows.
Screenshot:
It's hard to say without further information, but try to start the application with -Djavafx.verbose=true -Dprism.verbose=true and check if you get some error message which might help you.
Apparently, using SW rendering works fine. I am not sure how large the impact of SW rendering is.
I recently completed this website project: http://cunninghamk1.journalismanddesign.com/?page_id=150 It all seemed to work well for about a month, until I went back to it a few days ago. I haven't made any changes to anything on the site, except a bit of CSS related to the header.
On the examples and tutorials page, I have two data visualizations that no longer will draw. One (no. 3 on that page) is made with a Wordpress plugin, which I have updated. The other (no. 6 on that page) works with the Google Charts API. I don't see a commonality with the problems, and I'm not sure how to fix either one. I've redone the charts with Visualizer (the plugin) but I get the same error, which says 'undefined' is not a function (evaluating 'b.I()').
I've gone back to the .js file for this but nothing has changed or seems amiss otherwise.
Thanks for any ideas on what might be causing the problem.
I think this is just a bug in Xcode4.
When I click an error showed in the issue navigator, Xcode shows the line that contains the error in the editor view. But in some projects, Xcode opens the file that contains the error but never scroll to the line. It wastes my time and energies away a lot everytime...
It seems that some specific codes may cause this problem, but I can't figure out what it is. Anyone knows what may cause this problem or avoid it?