SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
Rob Spoor wrote:Welcome to the Ranch!
I suggest you strip out any non-UI code and turn it into an SSCCE (<= link), then post it here. If it's 258 lines with all the client code it should definitely be small enough as an SSCCE to post here.
Tom Grant wrote:
Rob Spoor wrote:Welcome to the Ranch!
I suggest you strip out any non-UI code and turn it into an SSCCE (<= link), then post it here. If it's 258 lines with all the client code it should definitely be small enough as an SSCCE to post here.
this good?
luck, db
There are no new questions, but there may be new answers.
Darryl Burke wrote:
Tom Grant wrote:
Rob Spoor wrote:Welcome to the Ranch!
I suggest you strip out any non-UI code and turn it into an SSCCE (<= link), then post it here. If it's 258 lines with all the client code it should definitely be small enough as an SSCCE to post here.
this good?
Nope. Did you go through the SSCCE page? The idea is that we can copy your code into a file, compile and run it to see where the problem might be.
Uncompilable snippets rarely reveal the problem; in fact, we often see here that the root cause of the stated problem was in code not initially posted.
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
Michael Dunn wrote:> oh i see now sorry :
do yourself a favor - create another class file, copy/paste your latest code and try to compile,
just as if you were someone else reading this thread.
most people, seeing the resulting error message/s, are likely to just click 'next', ignoring your problem.
I don't know what is supposed to show up, but if it is the buttons, this line won't help
for(i=0;i>button.length;i++){
as for the rest of the code, unless you've a career in code obfuscation, it's a shocker