SE17: SlickEdit-emulation F10 (menu selection) doesn't work...

[jbezem]

I was delighted to see that the default binding for F10 in SE-emulation (some debug command) was removed.
But now I found F10 to do not anything anymore. Until now I could remove the keybinding, to get the DOS-SE binding for menu selection, but for SE17 this doesn't work anymore. Am I doing something wrong?
If I cannot use 'F10-s-f' to start a "find" dialog (for instance), SE17 is unusable for me, since I've been using those combinations for 20 years now...

[Graeme]

Which version of Windows are you using?

[jbezem]

XP32, copy of "about SE":
SlickEdit 2012 (v17.0.0.8 32-bit)

Serial number: WB296420
Licensed number of users: Single user
License file: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\slickedit\17\slickedit.lic

Build Date: June 07, 2012
Emulation: SlickEdit (text mode edition)

OS: Windows XP
OS Version: 5.01.2600  Service Pack 3
Memory: 68% Load, 1379MB/2013MB Physical, 1211MB/3384MB Page File, 164MB/2047MB Virtual
Shell Info: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 1600 x 1200

Project Type: Cpp
Language: .c (C/C++)

Installation Directory: C:\Dokumente und Einstellungen\SBX631\Lokale Einstellungen\Anwendungsdaten\Apps\SlickEditV17.0.0\ (non-removable drive,NTFS,23519MB free)
Configuration Directory: d:\Eigene Dateien\My SlickEdit Config\17.0.0\ (non-removable drive,NTFS,31408MB free)

[Graeme]

F10 works ok for me on windows 7.
If I run slick with a brand new config folder I find that the default key binding for F10 is still debug-step-over.  Why do you think there's no default key binding any more?

Try running slick on a brand new config and see if F10 works  - temporarily rename your existing config folder.  If it works, maybe your config is corrupted somehow.  You can export and import just your keybindings if you want.  Did you have any problems when you ran slick V17 for the first time?

If that's not the problem, maybe you could try spy++ (if you have it) and see what messages get sent to slick for the F10 key.

Did you know that key bindings can select the mode they apply to - see the third column in the key bindings dialog?

Graeme

[Graeme]

uh, which emulation are you using?

[Graeme]

uh, which emulation are you using?

ok, I see you're using SE text mode edition  - a default config still shows debug-step-over for F10 on my system for that emulation.

[Graeme]

mmm, ok, now I think I see what the problem is.  If you remove all key bindings for F10, then in previous slick, pressing F10 would activate the main menu bar, but in V17 it doesn't.  It doesn't for me either.  Maybe there's a workaround.

[Clark]

You could press <Alt> with nothing else to activate the menu.

I'll try to fix F10 for the first point release.

[jbezem]

I hope the first point-release is coming soon, since the F10-key is so ingrained after 20 years that it's nearly impossible to switch to <Alt>. For my job, I'll stick to SE16 for now, and try to use SE17 only for my time-uncritical private projects.
Oh, and the F10 'debug-step-over' probably didn't appear since I used a converted *.sta from 16.0.3, I should have come up with that myself. Thanks to Graeme for clarifying the issue. +1

[Graeme]

If you're feeling brave you could try binding F10 to this function - it seems to work.

Code: [Select]

_command void try_this() name_info(',')
{
   if (_no_child_windows()) {
      _message_box("Sorry, gotta have a file open");
      return;
   }
   _mdi.p_child.mou_show_menu(def_mdi_menu);
}
 


[Clark]

This will be fixed in the first point release (~3 weeks).

[jbezem]

Thanks so far! And, yes, I do get the updates, but since I'm heavily busy these days (using 16.0.3), I'll try your temporary solution in the beginning of next week.
Since I haven't seen any complaints about this broken feature, I must be the only one still using the ancient emulation from those DOS-days...

[jbezem]

OK, it's taken a little while, but I tried Graeme's solution macro, and yes, it works. It takes a little getting used to, since a context menu opens when pressing F10, and a file needs to be open for it to work, but it works as described, and solves my immediate problem with SE17, thanks!
I'll give SE17 a new chance now, but I'm eagerly awaiting 17.0.1...

[jbezem]

Wonderful! 17.0.1 solves the issue. Thanks to Clark, but also to Graeme for providing a quick workaround! Both +1!