SlickEdit Community
SlickEdit Product Discussion => SlickEdit® => Topic started by: _fragment_ on June 12, 2012, 10:27:28 PM
-
Anyone else seeing this? Opening a file from explorer with the "open with" (Windows 7 64) when SE 2012 is not running opens the file with maximized screen. Then when I open another file using "open with" (SE is now running) changes SE to a smaller window that stays completey blank for a long time (sometimes it never refreshes) or until the window is minimized/restored or maximized to full size. Same thing happens with each additional file opened via the "open with" option in explorer. WTF?
Dave
-
No? Guess I'm the only one. Well, I suppose I'll have to go back to using v16 until the next update and hope it gets unbroken.
Dave
-
I specifically am not seeing that behavior. I'm running Win7 x64 with the brand-spanking-new SE 2012.
-
Experimenting, I find that it only happens if SE is minimized while I select a new file in explorer. If I have the explorer window sitting on top of the SE window, then it doesn't happen. Otherwise, it happens every time (after the first file).
Dave
-
I'm also encountering issues opening files from external tools (e.g. Windows Explorer) with Win7 x64 with SE 2012 (v17.0.0.8). In my case, the "current window" focus is *not* moving to SE when the file is opened. With V16, SE would get the cursor focus (current window), with V17, the focus stays in Explorer (or WinCVS).
Steve
-
I found what was causing my window open problem (as reported above, opening a file from Windows Explorer did *not* switch the Win 7 focus to SE). I didn't uninstall my V16 first and V17 doesn't remove the V16 linkages from the tools. So somehow V17 was intercepting the file open (that was really destined for V16) but it didn't get the window focus during that interception.
After I removed my V16 SE, V17 SE now gets the window focus.
Steve
-
I can confirm I'm seeing it Win7 x64.
Maximize SE.
Minimize it.
Open a file from Explorer
SE is restored to windowed mode and not maximized.
-
Good, one more piece of evidence that I'm not losing it!
-
I have this same problem. Has anyone been able to rectify?
-
I'd recommend opening a Support Case through the product web site, to make sure the development team sees this and has it in their issue tracking system.
This is a peer discussion forum, and although the dev team sometimes visits here, this isn't the best forum for filing bugs.
-
I'm still seeing this in 17.0.3.0 64-bit, so whatever they broke ain't fixed yet.