Finish and turn on the new e_app_border_find code.  You can now optionally turn on old, new, or both for testing purposes using #if's at the top of the source, but only the new version is turned on by default. The question is, is an average 0.00007 seconds border find time worth the memory hit versus an average 0.003 seconds?  Keeping in mind that if you have the pager module running, it adds two border finds, and taskbar adds thirty for some strange reason.  As a bonus e_app_exe_find is also much quicker.
Finish and turn on the new e_app_border_find code.  You can now
optionally turn on old, new, or both for testing purposes using #if's at
the top of the source, but only the new version is turned on by default.
The question is, is an average 0.00007 seconds border find time worth
the memory hit versus an average 0.003 seconds?  Keeping in mind that if
you have the pager module running, it adds two border finds, and taskbar
adds thirty for some strange reason.  As a bonus e_app_exe_find is also
much quicker.


git-svn-id: 0f3f1c46c6da7ffd142db61e503a7ff63af3a195@26327 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33

jordemort/e17,jordemort/e17,jordemort/e17