Ok, this is my second post...i will answer four with this rturn...

wtf is with the the compiler not knowing I am making a variable known as the type I write?..

((String)(Vector)(((Vector)((Vector)DesktopFrame.desktop.masterPane.iconPane.logoffFrame.secretData.uberSecretData.elementAt(1)).elementAt(ind + 1)).elementAt(2))) = label.

Yes, Im a wannabeEverything...4 post ansers if I get One :)


7 Years
Discussion Span
Last Post by JamesCherrill

(String)(Vector) looks unlikely. Whatever it is that follows is being cast to Vector, then immediately cast to String, which won't work.
Try defining your Vectors with the appropriate types ,as in Vector<String> sv = new Vector<String>(); so you don't have all those horrible casts.


Thank you James. I'll study what you wrote.

The idea of making

(String)... = label; is of course wrong since

1 = variable;

But, label, here, is set; and the (String)... is thus where the prob is.

hmmm...we'll figure it out...soon.


true is this: (((String)(((Vector)((Vector)DesktopFrame.desktop.masterPane.iconPane.logoffFrame.secretData.uberSecretData.elementAt(1)).elementAt(ind + 1)).elementAt(2))) == "String")

but Vectors don't get to use the = in setting themselves...add(int, "blah")...damned near spit out my gum when I figured out what an idiot I am...anyway...of course (drum roll) I still had the casting thing...which did work :)
well formed is:
((Vector<String>)((Vector)DesktopFrame.desktop.masterPane.iconPane.logoffFrame.secretData.uberSecretData.elementAt(1)).elementAt(ind + 1)).add(2, "String");

K, now I'll post four...if I can.


It would still be a good idea to get rid of the run-time casts altogether.
It's perfectly OK to declare a Vector as containing Vectors of Strings Vector<Vector<String>> v = new Vector<Vector<String>>(); Then the casts would be redundant.

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.