#define kapi_tipi 9 #define no_door 0 #define oto_door 1 // otomatik #define no_kapin_door 2 // y otomatik _ kapin kapi yok #define yes_kapin_door 3 // y otomatik _ kapin kapi var
#define kapi_asma_suresi 12 /*------------forosel suresi ------------------------------------*/ #define fotosel_suresi 13 /*----------------parallel kart seri kart ----------------*/ #define p_s_kart 14 #define p_kart 0 #define seri_kart 1 #define s_kart 1 // ayni seri kart
Posted on May 17, 2011 at 14:29 Yes I am sure the example : Parameters[14].value =0; not passed Parameters[14].value=1 ; it is ok only with zero ! thank you again
Simplify your code. Test your understanding of the debugger with simple variables then try using a structure. If assigning zero shows 48, what does assigning 1 show etc.
Posted on May 17, 2011 at 14:29 Thank you Clive ; I will test that tomorrow in the office ; but what is the difirence ? I used always to declare structures as in my example in many compilers and no problems .
I suggest you use variables that have bits set in every nibble e.g. 0x11111111, 0x22222222, ....etc. so you can tell if a variable is ''overflowing'' into another variable in your struct.
Then use the memory watch window set to the address of your structure. This will allow you to see what is happening at the lowest level.