nick stanish wrote:Oh? What am I missing?
I should explain where I'm coming from. The
SSCCE document (on which I'm somewhat of an authority) has some very specific requirements for code that calls itself an SSCCE. Those things are the words that make up the abbreviation.
The 1st
word is 'short'. A 'short' example of a compilation problem would not have 5 TextFields and Labels, but just 2. It would not have 5 images, but 2, or in fact, if that was not part of the compilation problem, it would not have any images at all.
Often in the process of shortening code, bugs can be discovered. That probably does not apply here, but if you trim out all the cruft, it makes the problem shorter to look at. It makes it easier to help.
The 2nd 'C' stands for 'Correct', which means it should show the same errors for you, as for me. When I went to compile the code, the first message I got was something to do with a missing } at the end of the code. Once that was fixed, the compiler reported a number of errors including the ones you described, but also others to do with the declared interfaces that had not been implemented. I began to comment them out, one by, when I struck yet another error that I could..
Then I thought, 'stuff this'. By the time I'd have your code anywhere near to producing the compilation errors you reported, it would no longer be the same code. I could just as easily write the code for you. But I have no intention of doing the latter, and since you could not make it easy for me to investigate the code as an SSCCE, I felt my efforts were best spent helping people that
can post an SSCCE.
So, ..I don't know where we can go from here. Can you produce something that is an SSCCE?