Guyz pls help...

Not really sure what you are describing but Arduinos do not have a real-time clock unless you add the module or shield.  You are running your processes off the counters or timers built in to the Arduino which can be held up by processing steps. Did you want to do a serial print to get the data out when the pin is read? I would put that in the sketch and look at the serial monitor.

Dennis,

Try to look my code,  whenever s1 r received 1/HIGH it performs the operation but it seem that it gives also 1 to other pins.. but eventually it really executes my desired output, only that it has a delay/trashes i guess,,

int s1= 16;

int s2= 17;

int s3= 18;

int s4= 19;

void setup(){

  Serial.begin(9600);

    pinMode(s1,INPUT);

    pinMode(s2,INPUT);

    pinMode(s3,INPUT);

    pinMode(s4,INPUT);   

    pinMode(7,OUTPUT);

    pinMode(6,OUTPUT);

    pinMode(5,OUTPUT);   

}

void loop(){

    Serial.println(digitalRead(16));  

    delay(500);

        int Rs1,Rs2,Rs3,Rs4;   

             Rs1= digitalRead(s1);

             Rs2= digitalRead(s2);

             Rs3= digitalRead(s3);

             Rs4= digitalRead(s4);

//    delay(3000);

     if (Rs1==1) {

     digitalWrite(7,HIGH);

     }

     else{

     digitalWrite(7,LOW);

     }

     if (Rs2==1) {

     digitalWrite(6,HIGH);  

     }

     else{

     digitalWrite(6,LOW);

     }

     if (Rs3==1) {

     digitalWrite(5,HIGH);   

     }

     else{

     digitalWrite(5,LOW);

     }

}

I would try to declare the int rs1,rs2,rs3,rs4; outside of the loop.  You should then initialize all them to HIGH or LOW.

When it goes through the IF statements, reset the variables so you know that baseline condition of your sensors. HIGH could mean 0 and not 1 depending on the sensor and may not be what you expect. Look up the sample code for switch debouncing.

I agree with Dennis. You could use a 50ms delay instead of 500ms. Also, what's the 3 second delay for? Maybe move the Serial.println to the bottom, after the program has gone through reading the states of the switches. Better for debugging if you do it after a switch is read, not before. Maybe the reason you are experiencing a delay between a pressed a switch and see the output is that 3 second delay. Try removing that altogether, and reducing the 500ms delay (which is half a second, easily noticeable) to 50ms, and let me know what you get.

Other than that, it's a straightforward sketch that compiles okay. Keep us posted!

~Gtr_Stitch