A little confused with Background in UIElements.

Thanks .. I just confirmed it every time I used the floats without the f it kept giving me a lossy error. If I put the the hard integers like 255 or 160, Netbeans accept it but made it pink for some reason so it confused me to what was going on. I just came back here to let you know it confirmed to work. Now If I could just turn the dang thing off.

Quote from james1bow

setBackgroundColor(0.1f, 0.1f, 0.1f, 0.75f);

you can do 0,0,0,0 or 1,1,1,1 but you need to 0.1f as 0.1 is a double 0.1f is float

I am starting to see double.

Thanks guys not knowing that there is a difference in the number ranges between the types was not the issue but rather, the notation to declare them with in statement notation ( ie. the f and d ), The API clearly says that the parameter argument s in public void setBackgroundColor(float r, float g, float b, float a) are floats. The problem was not even the calculation of the 0 to 1 requirement which is the desired RGB number (0 to 255) divided by 255.

The fact that any number between 0 and 1 was giving the same pink background results led to a further confusion. It was my error making the assumption that the Constructor would recognize the decimal form 0.62 (160/255) as in of itself a legitimate float. It requires the input to declare the decimal form number as f (Float), Further NETBEANS does not have the information to know the parameter argument can only be a valid float and determines that the decimal number can be either a float or double and assumes a double then flags a lossy conversion error and will not compile.

panel.setBackgroundColor(0.2f,1f,0.62f,0.8f); has no ERROR Flag

panel.setBackgroundColor(0.2,1,0.62,0.8); has an incompatible types: possible lossy conversion error from double to float. ERROR Flag

So NetBeans took the decimal numbers to be ,as default, doubles and would try to convert them to float during compile. I can only imagine at this point had NetBeans not assumed the decimals numbers are Double as default that this valuable reinforcement would not have been available on using notation and its requirement importance.

<posted this as clarification of the next person searching the forums for help on a UI panel background.>

Quote from yahwho

Welllllll, yes and no....

Anyways glad you have it sorted.

So you think 0.2 is NOT both an double and float possible number? but as far as sorted, yes I am too as it was annoying and significant progress has been made on my GUI.

So here is another similar issue.

exitbutton.setFontColor(50,999,999,50);

vs

titlepanel.setFontColor(0.125f,0.61f,0.11f,1.0f);

Neither gives an error in Netbeans.

The latter produces a greenish font the former a red one.

Quote from james1bow

possible yes. but if you do 0.2 its a double to java just like 0 can be a long or int but you will get errors casting 0 to long. to cast 0 long its 0L.

Ya well java default is double even though the only form the constructor can use is a float. Hence the lossy error. I appreciate the help as you have to realize I did this 8 years ago for the first time for about a year or two with this game then stopped and just now picking back up again. Prior to this my experience with programming was Fortran in University over 50 year ago and programmable controller logic, not as a programmer but as a Chief engineer designing heavy machinery with a team of 70. Seven or so were C++ programmers for proprietary embedded processors.

This is my fun hobby. Hope someone learns something from this discussion in java semantics because I certainly did as well as got my background colors on my GUI to be correct.