From: mfranz <mfranz>
Date: Thu, 2 Feb 2006 00:00:27 +0000 (+0000)
Subject: better use zero sensitive area to detect a missing (or inoperable) button,
X-Git-Url: https://git.mxchange.org/?a=commitdiff_plain;h=beff0cef609582cb6b865d90b2616f49bae973db;p=flightgear.git

better use zero sensitive area to detect a missing (or inoperable) button,
because a missing <button> default to 0, which makes a lot of sense
---

diff --git a/src/Cockpit/panel_io.cxx b/src/Cockpit/panel_io.cxx
index fe4ae4f02..40963f3d0 100644
--- a/src/Cockpit/panel_io.cxx
+++ b/src/Cockpit/panel_io.cxx
@@ -176,7 +176,7 @@ readAction (const SGPropertyNode * node, float w_scale, float h_scale)
   vector<SGPropertyNode_ptr>bindings = node->getChildren("binding");
 
   // button-less actions are fired initially, then fogotten
-  if (!node->hasValue("button")) {
+  if (!node->hasValue("w") || !node->hasValue("h")) {
     for (i = 0; i < bindings.size(); i++) {
       FGBinding b(bindings[i]);
       b.fire();