I noticed a long time ago that the position of function parameters and mouse cursor was incorrect. It’s strange that the “haxe” team doesn’t seem to plan on fixing it?
@785597448, if you’ve “discovered” an issue, please provide a simple code sample of the issue that others can replicate and verify.
This is an issue with the “API code prompt”, which does not affect the actual running of the code. However, beginners who learn a certain Xie library rely heavily on looking at prompts. If the cursor position of the parameter is not correct, it can be very strange. It seems that the “haxe” team is not considering fixing it ..
I discovered this issue a long time ago, and today, many years later, I have decided to provide feedback to the ‘haxe’ community, but have not received any response. The ‘haxe’ community seems to have no intention of fixing it
In addition to this issue, there are also some “haxelib” libraries that I mentioned before that have not been updated for a long time. Using these libraries has generated a lot of warnings during compilation, and some libraries cannot be used! When I personally saw it, the ‘haxe’ team didn’t seem very proactive in these directions. I just shared the problems I found with them
I don’t know what you’re referring to.
You didn’t give enough information for people to help you, we cannot read your mind.
So before you complain about how people aren’t interested in helping you, please answer the following questions:
What Haxe version are you using?
Which target do you compile to?
What libraries are you using?
What is the “certain Xie library”?
What is the “API code prompt”?
What class are you having issue with and how do you import it?
What are the compilation warnings, if any?
What is the part of your code that doesn’t work? Show it.
The Haxe ecosystem is large with many frameworks, libraries, and uses cases, if you don’t tell us what you’re using nobody can help you.
Though understand that Haxe is only a programming language, you might need to get help from the people making the framework/library you use if the issue is outside the standard library.
There are a large number of warnings when compiling “openfl” and “box2d” into “html5”! Nape cannot be used directly
Some libraries such as’ box2d nap 'have not been updated for a long time, resulting in a large number of warnings and errors
The second feedback is “haxe4.3.7”, the cursor position of the function parameter is incorrect!
Oh, you’re talking about a Visual Studio Code extension? I’ve noticed that offset. If you start typing the value of that next field, the blue highlight catches up, but I’ve just been making a mental note of what field I’m up to so it hasn’t really bothered me.
With respect to Box2D and Nape, your question was addressed in your other topic.
If you were to create a library and push it to Haxellib, then step away from maintaining it, it’s not the responsibility of the Haxe team to then look after it. It’s yours. But being open-source, with the source code available, if another developer chose to they can download the source code and update it themselves.
You can clone Box2D and Nape, and make the fixes you need to.
Also, if you used the git version of Box2D, you’d probably find those issues have already been fixed. In the example you shared above, you’re using version 1.2.3, not git.
I found an existing issue on GitHub for “signature help” (which is what VSCode calls that pop-up) highlighting the wrong parameter.