> "if you open the passenger door, then open the tailgate, then close the passenger door and press the lock button, the driver's door will lock but the passenger won't until you first unlock then shut everything"
I have a Jeep where the dome light logic has a problem like that. If you open a door, the dome light comes on. When all doors are closed, but the engine is not running, the dome light dims out after a delay.
If the engine is running or is started in the all doors closes, dome light on situation, the dome light goes out. If you open the tailgate, the dome light comes on as well. That's all normal.
But if I open a side door, then close it, and the light times out and dims, then, for some period of time thereafter, opening the tailgate will not turn on the light. I can just see some horrid mess of IF statements written in C behind this.
sdwr
State management is the only difficult problem in computer science
I have a Jeep where the dome light logic has a problem like that. If you open a door, the dome light comes on. When all doors are closed, but the engine is not running, the dome light dims out after a delay. If the engine is running or is started in the all doors closes, dome light on situation, the dome light goes out. If you open the tailgate, the dome light comes on as well. That's all normal.
But if I open a side door, then close it, and the light times out and dims, then, for some period of time thereafter, opening the tailgate will not turn on the light. I can just see some horrid mess of IF statements written in C behind this.