Function Key question

[seasoned_geek]

All,

In Scintilla.h we have

#define SCK_DOWN 300
#define SCK_UP 301
#define SCK_LEFT 302
#define SCK_RIGHT 303
#define SCK_HOME 304
#define SCK_END 305
#define SCK_PRIOR 306
#define SCK_NEXT 307
#define SCK_DELETE 308
#define SCK_INSERT 309
#define SCK_ESCAPE 7
#define SCK_BACK 8
#define SCK_TAB 9
#define SCK_RETURN 13
#define SCK_ADD 310
#define SCK_SUBTRACT 311
#define SCK_DIVIDE 312
#define SCK_WIN 313
#define SCK_RWIN 314
#define SCK_MENU 315
#define SCMOD_NORM 0
#define SCMOD_SHIFT 1
#define SCMOD_CTRL 2
#define SCMOD_ALT 4
#define SCMOD_SUPER 8
#define SCMOD_META 16

These values are then used in the standard shortcuts.

I'm curious as to why there aren't also SCK_F1 through SCK_F12

[Neil Hodgson]

seasoned_geek:

> In Scintilla.h we have
>
> #define SCK_DOWN 300

> …

> I'm curious as to why there aren't also SCK_F1 through SCK_F12

They weren't needed for the standard shortcuts. F keys are commonly left to define application-level functionality and not used for control actions.

Neil