![]() I've also included a button to read the states of the three multi-state buttons in my example. Better still, any number of states can be added with no extra lines of code, just add an image file and name it the next value. It basically just uses the tag of a button to hold the state of the switch. However I would like to offer my own solution and challenge others to come up with a simpler/better method. And hopefully you'll have fun doing itĪnyway, I'm surprised that this thread has not had more responses as there must be loads of ways of doing this and I don't know which is the best. Yes I agree that it is good to try and stick to certain standards and conventions to make it easier for others to follow your code, but at the end of the day, if it works and you're not expecting someone else to have to continue the project then its up to you how its done. That's why programming is like handwriting, we all have our own style and way of doing things. But at the end of the day they will all say roughly the same thing. Some will be neat and others barely legible, and some will undoubtedly contain spelling errors. you can give several people a paragraph to copy, some people will choose to write in capitals, others may write joined-up (cursive), or some may chose to write it in their native language. I often say to colleagues and friends that programming is like handwriting. Circuit synthesis, constraints, synthesis for FPGA, time simulation.I'd like to offer my own solution to the problem and at the same time share with you an analogy I use to describe coding/programming.Circuits modeling and event based simulation, circuit testing, test design, functional simulation (ModelSIM), co-simulation. ![]()
0 Comments
Leave a Reply. |