paweld/lazarus
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/lazarus/lazarus.git synced 2025-06-06 00:18:18 +02:00
Code Issues Packages Projects Releases Wiki Activity

cocoa: removing tabControl workaround

Browse Source 
git-svn-id: trunk@59058 -
This commit is contained in:
dmitry 2018-09-17 22:43:37 +00:00
parent f000038a2b
commit b64daa1f84
1 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
lcl/interfaces/cocoa/cocoatabcontrols.pas
View File

@ -110,7 +110,6 @@ type
tabView: TCocoaTabControl;
tabPage: TCocoaTabPage;
procedure setFrame(arect: NSRect); override;
function nextResponder: NSResponder; override;
end;
function IndexOfTab(ahost: TCocoaTabControl; atab: NSTabViewItem): Integer;
@ -320,30 +319,6 @@ begin
inherited setFrame(arect);
end;
function TCocoaTabPageView.nextResponder: NSResponder;
begin
// by default nextResponder would return the parrent.
// for TCocoaTabPageView this would be NSTabView (TCocoaTabControl)
// (or NSView*, that would eventually return NSTabView)
//
// When processing keyboard events, and processing Control-Left or Control-Right
// Window finds a NSTabView amongn "the chain of responders", it would
// execute moveLeft: or moveRight: methods of that NSTabView,
// instead of delivering Control-Left to the firstResponder.
// Thus affecting any focused control that depends on Ctrl+Left, Ctrl+Right
// (namely TSynEdit).
//
// So the solution is to prevent NSTabView be available in "chain of responders"
//
// Test: Create a form -> place TTabControl on it with 1 page -> put SynEdit on it
// See if TSynEdit can process Ctrl+Left, Ctrl+Right
//
// * NSView would be returned if TCocoaTabPageView is added as a child
// for a view of a tab, instead of being assigned as a view of a tab
if Assigned(tabView) then Result := tabView.nextResponder
else Result:=inherited nextResponder;
end;
{ TCocoaTabPage }
function TCocoaTabPage.lclGetCallback: ICommonCallback;