Is there a way (filter settings, etc) to see only JavaFX related bugs in the JDK Bug System?
Also, the Reporter names seem to be gone. Now I'm "J. Duke", I guess like everyone else that doesn't have an acount there. So how do I find the bugs I reported?
Sample JavaFX issue query string:
https://bugs.openjdk.java.net/issues/?jql=project%20%3D%20JDK%20AND%20component%20%3D%20javafx
Created by:
Browse to: https://bugs.openjdk.java.net/browse/JDK
Click on All Issues
Click on + More Criteria
Check Component
Click Component drop-down.
Check JavaFX
Reporter also works in advanced (jql) mode (reporter = 'your name'). Find one of your issues by other means and then copy your name as it is displayed there. Worked for me.
Related
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.
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
None of the other questions regarding this question were able to answer this. I am new to programming, and I am just trying to add a FacebookLogin option to the website.
I built all the Javascript they wanted, and there is no error there(I don't think). In the interest of saving time, and that I am working on multiple computers. I am going to post pictures of all the code. I have added excess using statements to try and get the reference.
http://imgur.com/a/2wCyf
If you need anymore information let me know. And I will edit this page.
it looks like you just have some simple issues to fix in your IDE/project. The below instructions are for Visual Studio, but can be slightly altered for other IDEs.
First, make sure you have a reference to the Facebook SDK for .NET (I'm assuming you're using Outercurve's library from the looks of it):
In Visual Studio, check in the Solution Explorer window, then expand the "References", and make sure you see it there.
If it's not there, right-click "References", then "Manage Nuget Packages". When the Packages screen pops up, ensure in the left-pane that you have "Online -> nuget.org" selected. In the top right of the Packages window, in the "Search Online" textbox, enter:
facebook sdk and press "enter". On my screen, it's the second search result. To ensure you have the correct one, ensure that the "Created by" field says "Outercurve Foundation" before you accept it. Once you know you have the right package, hit the "Install" button, and it will be added to your project.
Once you have verified you have the correct reference, if you are still having the issue, make sure you have a "using" statement in your class file, to ensure library types you are using are recognized. In this example, I believe that would be:
using Facebook;
From the images of code you provided, I didn't see that statement in there, so that may be the problem, if this is fact the library you are referencing.
I am new to this type of application but what I found that is:
Use Facebook.FacebookClient instead of FacebookClient.
Running Analyze in Xcode 4.0.2 shows issues in the Issue Navigator. Clicking on an issue makes the appropriate file appear in the Editor pane, but nowhere does it show where in the code the issue occurs as I am used to from Xcode 3.x. Does anyone know how I can turn on this feature?
A couple of tips:
First, if you're looking for the view where Xcode annotates the project with arrows, bear in mind that you may need to expand the top-level analyser result in Xcode's Issue navigator and click the second-level issue in order to see those - see screenshots.
Screenshot 1: top-level issue selected - no arrows
Screenshot 2: second-level issue selected - arrows!
Second tip: if that stuff isn't working, try cleaning the project's build products folder. Hold down the Option (alt) key and choose Clean Build Folder... from the Product menu. (You need to hold down the Option key, otherwise you won't see that menu option.)
I've seen this happen before sometimes. I believe it's a bug in Xcode. Restart Xcode and try again.
One note. I'm seeing this for files that are referenced outside the current project. I currently have a library in which the files with missing annotations live and simply added them to my current project without copying them. Haven't done the project dependency setup yet, so if you're referring to files outside your project that could be why. (I opened the library project, did an analyze and the annotations showed up.)
Woohoo, I've nailed it! At least for me. I've been struggling with this problem for about 2 hours now, trying out all the things suggested here and more (Xcode 4.0.2, Snow Leopard). Bizarre thing was I had one file where the warning were correctly showing in the editor. Then I noticed the difference to all other files; in the File Inspector pane the location was specified as "Relative to Project" (warnings show correctly in the editor), all the other project files were "Relative to Group" (warnings not showing in the editor).
I took one of the problem files, switched it's location to "Relative to Project", reanalyzed and bingo! I've see it's warnings in the editor.
I guess this ties in a bit with David Goodine's answer refering to files outside the project.