[Bug 40860] New: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly
https://bugs.winehq.org/show_bug.cgi?id=40860 Bug ID: 40860 Summary: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ramonrafe(a)gmail.com Distribution: --- Problem: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly. Importance: Normal. ------------------------------------------------------------------------ Hello. I've installed Lazarus 1.6 for Windows on Wine in Linux Mint 17. Lazarus compiles well, although the function keys F11 and F12 don't work like in Windows. F11 (en Windows) makes visible and active the window with the component inspector. The cursor goes to the window and the window changes to be on top. F12 (en Windows) switch betwen the editor of code and the form associated to that code. The cursor goes to the window and the window changes to be on top. When F11 or F12 are pressed (in Lazarus on Wine), the cursor goes to the window, although the window doesn't change to be on top. So, if there are other windows over it, you won't be able to see the window with the cursor. It doesn't happen in Windows. In Windows, when you press F11, the window component inspector pass to be the window with the cursor and the window pass to be the window on top. It looks like a minor problem, although this limitation makes Lazarus not usable in the practice or very unfriendly for use it. Sorry for my basic English. Thank you very much. Ramón. ---------------------------------------------------------------------- Linux Mint: Linux Mint 17 Qiana Wine: version 1.6 and 1.8 . Lazarus 1.6: - File: lazarus-1.6.0-fpc-3.0.0-win32.exe - Link: http://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits/... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 --- Comment #1 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Does the following staged patch set help? https://github.com/wine-compholio/wine-staging/tree/master/patches/winex11-_... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 --- Comment #2 from Ramón Ramos Fernández <ramonrafe(a)gmail.com> --- (In reply to Dmitry Timoshkov from comment #1)
Does the following staged patch set help? https://github.com/wine-compholio/wine-staging/tree/master/patches/winex11- _NET_ACTIVE_WINDOW
Hi Dmitry. Thank you very much for your answer. I'm a newbie, so I'm not sure about what to do with the information of your answer. Is this way (explained on this link: https://wiki.winehq.org/Patching ) the way I should use your information?. And, if so: - Should I use the two files? - Should I use the original names with the extension "patch"?. Many thanks again. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 --- Comment #3 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Ramón Ramos Fernández from comment #2)
Hi Dmitry. Thank you very much for your answer. I'm a newbie, so I'm not sure about what to do with the information of your answer. Is this way (explained on this link: https://wiki.winehq.org/Patching ) the way I should use your information?. And, if so: - Should I use the two files? - Should I use the original names with the extension "patch"?. Many thanks again.
To make the testing easier (and completely avoid the patching/compilation steps) you could use a pre-built wine-staging package (which already includes the aforementioned patches). Please look for instructions suitable for your distribution at https://github.com/wine-compholio/wine-staging/wiki/Installation -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 --- Comment #4 from Ramón Ramos Fernández <ramonrafe(a)gmail.com> --- Hi again, Dmitry. I've installed Wine Staging with these terminal commands (found on : https://libuntu.net/2015/08/14/wine-staging-instalacion-pruebas-y-conclusion... ) sudo add-apt-repository ppa:pipelight/stable sudo apt-get update sudo apt-get install –install-recommends wine-staging sudo apt-get install wine-staging-compat And the problem has been solved. Thank you very much for your help. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/winex11-_NET_A | |CTIVE_WINDOW Ever confirmed|0 |1 Status|UNCONFIRMED |STAGED --- Comment #5 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Ramón Ramos Fernández from comment #4)
Hi again, Dmitry.
I've installed Wine Staging with these terminal commands (found on : https://libuntu.net/2015/08/14/wine-staging-instalacion-pruebas-y-conclusion... )
sudo add-apt-repository ppa:pipelight/stable sudo apt-get update sudo apt-get install –install-recommends wine-staging sudo apt-get install wine-staging-compat
And the problem has been solved.
Thank you very much for your help.
No problem, I'm glad that it worked for you. Marking this bug appropriately. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #6 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Ramón Ramos Fernández from comment #4)
Hi again, Dmitry.
I've installed Wine Staging with these terminal commands (found on : https://libuntu.net/2015/08/14/wine-staging-instalacion-pruebas-y-conclusion... )
sudo add-apt-repository ppa:pipelight/stable sudo apt-get update sudo apt-get install –install-recommends wine-staging sudo apt-get install wine-staging-compat
Btw, I'm not sure if there is a (significant) difference between the pipelight and wine-staging repositories (adding Sebastian to cc:, perhaps he could clarify things a bit), but according official instructions at https://github.com/wine-compholio/wine-staging/wiki/Installation#-ubuntulinu... the recommended repository for wine-staging is $ sudo add-apt-repository ppa:wine/wine-builds $ sudo apt-get update $ sudo apt-get install --install-recommends wine-staging -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 Ramón Ramos Fernández <ramonrafe(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|STAGED |RESOLVED --- Comment #7 from Ramón Ramos Fernández <ramonrafe(a)gmail.com> --- I think that the problem has been solved. I'll change the status to "Resolved" and "Fixed". Thanks again. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #8 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Well, the status should not be FIXED (since the unpatched plain wine doesn't work for you), it should be either STAGED, or this bug should be marked as a duplicate of another already staged bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40860 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #9 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with vanilla wine-4.5? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org