Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion #14142: wxOSX-cocoa: No EVT_KILL_FOCUS events
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
wxTrac  
View profile  
 More options Oct 7 2012, 4:39 am
From: "wxTrac" <nore...@wxsite.net>
Date: Sun, 07 Oct 2012 08:39:01 -0000
Local: Sun, Oct 7 2012 4:39 am
Subject: Re: #14142: wxOSX-cocoa: No EVT_KILL_FOCUS events
Ticket URL: <http://trac.wxwidgets.org/ticket/14142#comment:4>

#14142: wxOSX-cocoa: No EVT_KILL_FOCUS events
-----------------------------+--------------------------------------------- -
 Reporter:  robind           |       Owner:  csomor  
     Type:  defect           |      Status:  accepted
 Priority:  normal           |   Milestone:          
Component:  wxOSX-Cocoa      |     Version:  2.9-svn
 Keywords:  OSX cocoa focus  |   Blockedby:          
    Patch:  0                |    Blocking:          
-----------------------------+--------------------------------------------- -
Changes (by csomor):

  * owner:  => csomor
  * status:  new => accepted

Comment:

 ok, I found the reason for the seeming late kill focus, it isn't related
 to the deactivating of the window

 (which IMHO wouldn't have to trigger a kill focus, since I might be in a
 partial edit, having to look something up in a different app and come back
 to finish editing in the same field, only when really leaving the field, a
 validation would make sense, but I'll bow to crossplatform behavior here -
 so I'll model it after msw if this behaves differently)

 the reason for focus kill is the wxFrame::OnActivate when coming back
 which sets the focus explicitly, therefore triggering a focus kill... I'll
 run the same on msw and compare ...

--
Ticket URL: <http://trac.wxwidgets.org/ticket/14142#comment:4>


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.