Valgar: you wrote:
About the other problem....i think that for my skill as a programmer i have made a code too big....and now i don't know where's the bug :P
Tup for troubleshooting code. When writing code, change one thing at a time, so that if a problem occurs, you know at what point the problem occurred. When you have code that is already too big and are not sure how to track down the problem, try isolating code segments and try them one at a time. For example, put some blank lines before and after a segment you want to isolate. Use that old fashion command GOTO, and then a label at the point you want it to goto. You can thereby jump over sections, and fine tune which segments you want to try out independent from the rest of the code. Hope this helps.
About the other problem....i think that for my skill as a programmer i have made a code too big....and now i don't know where's the bug :P
Tup for troubleshooting code. When writing code, change one thing at a time, so that if a problem occurs, you know at what point the problem occurred. When you have code that is already too big and are not sure how to track down the problem, try isolating code segments and try them one at a time. For example, put some blank lines before and after a segment you want to isolate. Use that old fashion command GOTO, and then a label at the point you want it to goto. You can thereby jump over sections, and fine tune which segments you want to try out independent from the rest of the code. Hope this helps.