Hello,

yeah, thanks.

Ctrl-t doesn't help to find the error.

I even made a tool in Word-VBA to count my { and } and they are the same in all tabs...
(or count "(" and ")" - didn't help).

Processing didn't even throw an error when I had a return(x); in my void function...

Maybe I need to switch to eclipse after all.

The Code is spread over so many tabs that I hesitate to post it since there's no tool in the IDE to copy the content of all tabs at once to the clipboard. But it would just be too many lines for the forum I guess anyway.

I am still stuck but I will find it.

The error I get appears at the wrong place and has the wrong content since the { and } are ok but the (t)error message is referring to them. Therefore it is a little hard to find.

Greetings, Chrisir

You can try and export the sketch to get one whole Java file. Although it might not work in your case (parsing error).

@quarks :
I did (1)
I did (2) - vba-code works fine, but finds no errors (checking pairs of [] {} ()   )

@phi.lho :
no export possible



Maybe It's another mistake,

•  = instead of ==
• or one comma to much

Hello!

I found it!!!!!!!!!!!!!

it was a missing if in a place

where "else if" should've been:

1. else if (someBoolean) {

was expected.

And the IDE wasn't able to give an error message right there but just throw an error
at the end of 2nd tab from the left...  

all the brackets showed up as expected:

1. void mousePressed() {
2.   if (mouseButton == LEFT) {
3.     // LEFT Button
4.     if (programIsStarting) {
5.       programIsStarting=false;
6.     }
7.     else
8.     {
9.       if (programState == programStateGetInput) {
10.         initialMouseValue.set(mouseX, mouseY, 0);
11.       }
12.       else if (programState == programStateNormal) {  // here if was missing
    
13.         halten = true;
14.         startPoint.x=mouseX;
15.         startPoint.y=mouseY;
16.         boxPos.x=mouseX;
17.         boxPos.y=mouseY;
18.         boxPos.z=100;
19.       } // else if
20.     } // else
21.   } // LEFT
22. } // func

Lessons learned:

• use save as... more often
• use archive sketch from menu Tools more often
  
• to identify errors, use run more often, when it doen't run anymore look into the last place you changed
• to identify errors, use my word vba - it's free
  
• to identify errors, eliminate long passage with /*  */ and try running it then - when it does, the error is within the passage
• then make this passage smaller with /*  */ and try again - still running? Or not anymore? Then this was the passage.

Thanks for all the help! 

Chrisir