Author Topic: edit window doesn't get focus at startup  (Read 301 times)

Graeme

  • Senior Community Member
  • Posts: 2718
  • Hero Points: 337
edit window doesn't get focus at startup
« on: August 02, 2021, 11:47:43 am »
The edit window doesn't get focus at startup.  instead, focus is on a toolwindow  - a floating group of toolwindows  - whichever one was last active before closing slick.
This is the same as V25.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3604
  • Hero Points: 480
Re: edit window doesn't get focus at startup
« Reply #1 on: August 02, 2021, 04:36:48 pm »
Which platform?  Can you determine which tool window is holding focus (hit Tab to cycle focus through controls).  Is the tool window holding focus docked or floating?

Graeme

  • Senior Community Member
  • Posts: 2718
  • Hero Points: 337
Re: edit window doesn't get focus at startup
« Reply #2 on: August 02, 2021, 11:00:47 pm »
Windows 10 64 bit.  I've reproduced the problem with a clean config by opening a bunch of floating tool-windows  - see screenshot or open the attached config zip.  The toolwindow that gets the focus is search results - but in my normal slick 25.0.2 config it is preview/ references/ backup history  - whichever one of this group was last in front when I closed slick  - so it's probably not the focused tool-window that causes it.  It's fairly minor, I've put up with it for a while.


Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3604
  • Hero Points: 480
Re: edit window doesn't get focus at startup
« Reply #3 on: August 02, 2021, 11:15:04 pm »
Reproduced.  I have a potential fix, but I'm having someone smarter than me look it over first.
« Last Edit: August 03, 2021, 12:08:16 am by Dennis »

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3604
  • Hero Points: 480
Re: edit window doesn't get focus at startup
« Reply #4 on: August 03, 2021, 01:13:08 pm »
Fixed for BETA 2.  Thanks for reporting this.  I never use floating tool windows, so I would not have noticed the issue.