Bug #176

avoiding window 'ghosting' in mouse tracking loops

Added by J. Templ over 1 year ago. Updated over 1 year ago.

Status:ClosedStart date:09/20/2017
Priority:NormalDue date:
Assignee:J. Templ% Done:

0%

Category:-
Target version:1.7.1
Forum topic:https://forum.blackboxframework.org/viewtopic.php?f=40&t=676

Description

When selecting text or in general whenever a mouse tracking loop takes longer than 5 seconds,
Windows thinks that the application is not responding and turns the application window into
a 'ghost' window. This happens in particular with Windows 10 but there are also cases in
XP and Vista where ghosting occurs.
It is proposed to change this behavior by consuming all Windows messages while mouse tracking.
Only mouse messages will be processed, though.
Problem reported by Doug Danforth & Robert Campbell.

Associated revisions

Revision 42f94ad4
Added by J. Templ over 1 year ago

avoiding window 'ghosting' in mouse tracking loops. Refs: #176.
Rider.Input now consumes all messages in order to avoid Microsoft Windows 'ghosting'
behavior in BlackBox's modal mouse tracking loops.
Only mouse messages directed to the target window are processed,
other messages are ignored.

Signed-off-by: Josef Templ <>

Revision 8705a6be
Added by R. Campbell over 1 year ago

Merge pull request #187 from BlackBoxCenter/issue-#176

avoiding window 'ghosting' in mouse tracking loops. Refs: #176.

History

#1 Updated by J. Templ over 1 year ago

  • Forum topic set to https://forum.blackboxframework.org/viewtopic.php?f=40&t=676

#2 Updated by R. Campbell over 1 year ago

  • Description updated (diff)

#3 Updated by R. Campbell over 1 year ago

  • Status changed from New to Closed

Also available in: Atom PDF