//1.Tapping cancel will trigger Query::run twice
Log:
resetPrimaryNavigationTag()
Filters changed
Scope::processPrimaryNavigationTag(): tag is ' "" '
active filters count: 0
invalidateResults ---> Sender: QObject(0x0)
Dispatching search: "untitled10.gary-wzl77_untitled10" "" ""
Scope:: query // 1
invalidateResults ---> Sender: QTimer(0x16be7d8)
Dispatching search: "untitled10.gary-wzl77_untitled10" "" ""
[2016-05-04 14:11:05.624] ERROR: untitled10.gary-wzl77_untitled10: QueryBase::run(): Operation was aborted by an application callback: Callback aborted
Scope:: query // 2
The second run is caused by m_typingTimer. I think the proper fixing should be not to trigger timeout from m_typingTimer when query string is empty e.g Tapping cancel.
//1.Tapping cancel will trigger Query::run twice
Log:
resetPrimaryNav igationTag( ) processPrimaryN avigationTag( ): tag is ' "" ' gary-wzl77_ untitled10" "" ""
Filters changed
Scope::
active filters count: 0
invalidateResults ---> Sender: QObject(0x0)
Dispatching search: "untitled10.
Scope:: query // 1
invalidateResults ---> Sender: QTimer(0x16be7d8) gary-wzl77_ untitled10" "" "" gary-wzl77_ untitled10: QueryBase::run(): Operation was aborted by an application callback: Callback aborted
Dispatching search: "untitled10.
[2016-05-04 14:11:05.624] ERROR: untitled10.
Scope:: query // 2
The second run is caused by m_typingTimer. I think the proper fixing should be not to trigger timeout from m_typingTimer when query string is empty e.g Tapping cancel.