You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
splitter position is incorrect based on its percentage if splitPaneLayout just occupy a portion of the screen #22
Having some views above and below the splitPaneLayout, i.e. a toolbar and a navigationBottomBar, then SplitPaneLayout doesn't calculate correctly the position of the splitter the first time it is loaded.
changed the title [-]splitPaneLayout doesn't posittion on its defined percentage if it just occupy a portion of the screen[/-][+]splitPaneLayout doesn't correclty gets splitter position on its defined percentage if it just occupy a portion of the screen[/+]on Mar 4, 2020
changed the title [-]splitPaneLayout doesn't correclty gets splitter position on its defined percentage if it just occupy a portion of the screen[/-][+]splitter position is incorrect based on its percentage if it just occupy a portion of the screen[/+]on Mar 4, 2020
changed the title [-]splitter position is incorrect based on its percentage if it just occupy a portion of the screen[/-][+]splitter position is incorrect based on its percentage if splitPaneLayout just occupy a portion of the screen[/+]on Mar 4, 2020
Activity
[-]splitPaneLayout doesn't posittion on its defined percentage if it just occupy a portion of the screen[/-][+]splitPaneLayout doesn't correclty gets splitter position on its defined percentage if it just occupy a portion of the screen[/+][-]splitPaneLayout doesn't correclty gets splitter position on its defined percentage if it just occupy a portion of the screen[/-][+]splitter position is incorrect based on its percentage if it just occupy a portion of the screen[/+][-]splitter position is incorrect based on its percentage if it just occupy a portion of the screen[/-][+]splitter position is incorrect based on its percentage if splitPaneLayout just occupy a portion of the screen[/+]Fix for issue MobiDevelop#22
vyguera commentedon Mar 4, 2020
This is fixed in pull request #24