| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #3147
| Application: | FLTK Library |
|---|
| Status: | 2 - Closed w/o Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | WIN32 |
|---|
| Summary: | Assigning Ctrl+Shift+0 to a Fl_Sys_Menu_Bar item does not work using Visual Studio 2012 |
|---|
| Version: | 1.3.3 |
|---|
| Created By: | roukaour |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | None |
|---|
| Fix Commit: | n/a |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | roukaour
20:50 Nov 04, 2014 |
| I am using FLTK 1.3.3. My application has a Fl_Sys_Menu_Bar, and one item has the shortcut FL_COMMAND + FL_SHIFT + '0'. This shortcut works on a Xubuntu 14.10 machine when compiled with g++, and on a Windows 8.1 x64 machine when compiled with Visual Studio 2013 Update 3. However, on a Windows 7 x64 machine and a separate Windows 8.1 Update 1 machine, both using Visual Studio 2012 Update 4, the shortcut does nothing, although clicking the menu item works normally. Using keys other than '0', like 'g' or '2', also works as expected. I do not have a second widget assigned the same shortcut. Is this reproducible, and is VS 2012 actually responsible? | |
| |
| #2 | roukaour
21:08 Nov 04, 2014 |
| Apologies, this is a duplicate of STR #3146 (although I have found Visual Studio 2012 to be the common denominator here, not Windows 8.1). Please merge them or delete one. | |
| |
| #3 | AlbrechtS
05:23 Nov 21, 2014 |
| FTR: STR 3146 has been closed. | |
| |
| #4 | AlbrechtS
09:35 Apr 16, 2024 |
| I'm sorry to say that this STR is too old to be worked on. Visual Studio 2012 is too old to reproduce the issue on a modern system.
We do also no longer fix low priority bugs in 1.3.x, we're concentrating on 1.4.0 and higher.
If this STR still needs resolution with FLTK 1.4 (currently Git only) and a recent version of Visual Studio (VS 1019 or VS 2022 which are still supported by Microsoft), then please open a GitHub Issue and post a small program that reproduces the issue. Thanks in advance.
Thanks for your understanding. I'm closing this STR now (w/o Resolution). | |
| |
| #5 | AlbrechtS
10:18 Apr 16, 2024 |
| Sorry for the typo, this should obviously read:
... a recent version of Visual Studio (VS 2019 or VS 2022 ...) | |
[ Return to Bugs & Features ]
|
| |
