So I have been trying to use the sdk. I like the qol features it has but I have been having this crazy issue that is driving me mad. So mad I already installed eclipse and idea community and am working out ways to avoid the sdk.
Now this is probably not a sdk issue probably a net beans issue but it involves the auto filled params on methods.
For instance I go to call set local translation and all the param are named speed… I go to call set material and it is named guinode…
This is absurd it would not bother me if the feature worked like VS and gave you the names of the arguments so you know what you need to pass in but arbitrary names just drive me crazy as I need to constantly check what the param actually are and make sure I am calling the right method.
You see the parameter names if you press Ctrl-Space while writing the name of the method (i.e. before you actually type the opening bracket for the parameters. As for the auto-fill, the IDE tries to find fitting fields or variables to put into the method parameters. Depending on how your code looks for me this works out pretty well most of the time. Otherwise you just keep on typing and fill in the parameters you want. I don’t exactly get what the issue is?
The issue I am having is I get the method from the drop down and it is auto filling the names with variables not even in the code and as I am learning it just makes things more complicated. The autocomplete is just giving me random arguments. I tried a uninstalled and deleting all settings and cache files everywhere. It still insisted every param is named speed or guinode.
Edit: Also note it could just be me not liking the feature in netbeans. I am not a fan and never have been most of the time I code in C/asm using VS or eclipse as my core hobby is microcontroller firmware using avr’s and arm chips. Feels like the idea is stepping all over my code and I can’t find a option to turn it off.
Correct I am just learning no need to get over complex yet. I would never do that for a real project. I am supprized that feature would pull info from a extended class. Why not just give the tabable list the argument names from the method… weird ide feature.
@perJin
Thanks talk about hidden will make sure to turn that off.
That’s funny I always found NB superior because of this feature :p.
Sometimes it can be a bit lame like in your situation, but it works really well when you are in short method with local variables.
I work/worked with NB,IDEA and eclipse, developing in java, and tbh I still feel that NB is the best at it, don’t give up on it yet ;).
I understand I am more from the very little IDE support camp ie. just basic functionality in the case of say ARM with a eclipse setup. You get dot completion and can see the param names nothing really more and the exceptional completion in the case of Visual Studio with AVR where the “auto fill feature of netbeans” in visual studio it fills the brackets with the function argument names that exist in the library and you tab through and replace them with what you want. Never before this saw a IDE try to guess what arguments you want to pass in. Just so happens in my case it keeps giving me garbage argument fills and I find it annoying.
Maybe this is what you guys meant when you said SimpleApplication is a mess lol.
Actually, all of the protected fields really IS the reason I hate SimpleApplication from a support perspective. This SDK issue is just a harmful side-effect that users happen to notice, too.
@pspeed is there any specific reason all the protected fields were put there to begin with? Personally when I do OOP which I hate in general I try to avoid that crap. Usually I would prefer to just composition in to build myself a base object or if I need more abstraction I would pass in a pointer to a external object to attach it to a more globally avaliable state management system. So much cleaner and flexible being able to swap in and out various systems as needed.
@pspeed yea I can relate as I am trying to learn enough about the engine to start on my game. I really want to start but I at the same time want to ensure I know enough about the way things work that I do not code myself into a corner.
Yup I agree but there is always the risk of permenent corners that force a total do over if you don’t know what you are doing. Luckily I am starting with a card game nothing inherently huge.
Need to figure out this app state stuff that is the biggest hurdle for me atm. Need to learn how these app states are used.
