Triangles are for decisions, not statements. Your flow chart is ONE-TIME only. Do you want to process only one time? IF more than once, you need a loop back to some beginning point.
Paul
The rectangles rotated 45 degrees should contain a test. Could be
if (data > limit)
.
There are always 2 exits. One Yes and one No. Each of them is followed by som code.
After the correct "delay(200)" such a test block is needed in order to decide for ++ or --.
The diagram could start with a "normal block" like "readButtons" followed by a test blocks "if (button1)", a Yes or No exit. The No will then test for "button2".
Pleas post updated pictures in the last post.
That diamond is not used correctly. Read my previous reply.
The connection from the bottom up backwards is fine. You need a block updating where lastbutton state gets its value and "buttonstate" gets its new value.
Thinking the right way, the order how variables change, will be clearly visualized in the flow chart and save lots of debugging.
You need to go to the google school of flowcharting.
Srsly, thus looks like you saw a flowchart at some point in your life and now you are totally winging it. Your diagram is nearly meaningless and certainly is not useful for programming or documentation.
Find some tutorial that matches your learning style and get a grip on basic flowcharting.
I moved from an all IBM service bureau to another service bureau that was mostly Burroughs computers, but they did have an IBM 360-30. None of the programmers had a flow charting template. Hard to imagine. No one knew the templates and lots of other stuff was free from IBM if you had an IBM computer.
I ordered 6 or 7 plastic templates. A few weeks later a large package arrived from IBM. Was full of plastic templates. I had failed to notice the product number had a dozen quantity for the order. So, 6 or 7 times 12 gave everyone at least one template!
Paul