title: QML Cannot emit signal if it has same name as property
body: <p>I was trying to wrap a <code>MouseArea</code> to customise it's behaviour and came across a strange issue.  The example code below demonstrates the problem:</p>
  
  <pre><code>import QtQuick 2.3
  
  Item {
      id: base
      width: 100
      height: 100
      anchors.fill: parent
  
      property alias pressed: area.pressed
  
      signal pressed( var mouse )
  
      MouseArea {
          id: area
          anchors.fill: parent
  
          onPressed: {
              base.pressed( mouse );
          }
      }
  }
  </code></pre>
  
  <p>Clicking in the rectangle results in this error:</p>
  
  <blockquote>
    <p>TypeError: Property 'pressed' of object QmlTest_QMLTYPE_0(0x1b4c780) is not a function</p>
  </blockquote>
  
  <p>Clearly it's trying to call the property <code>pressed</code> rather than the signal <code>pressed</code>.  Is there a workaround for this?  Bear in mind that the interface has to mimic <code>MouseArea</code> so there needs to be a both a <code>pressed</code> property <em>and</em> signal.</p>
  
  <p>This does strike me as a bug, as clearly <code>MouseArea</code> manages it, but it is declared from C++.  I know that the usual answer to any slightly complex QML question is "do it in C++", but because the great majority of QtQuick classes are private, it's usually not practical.</p>