Yes, I don’t expect you on this. Thank you for sharing the current situations.
This is a critical problem to me. My understanding is currently the Wayland support code integrates glvnd. Can I use mesa by other means than BGLView?
1 Like
No. Haiku Wayland compat layer to not deal with EGL at all, it just accepts wl_shm bitmaps. Wayland EGL will work if compile Mesa with Wayland support, thats all. But again, it need updating Mesa package.
Eliminating Wayland will not make getting GTK OpenGL support easier. Mesa EGL support is real issue.
3 Likes
Thank you. I will investigate them.
4 Likes
I managed to generate an xkb keymap based on the system ones with full support for all modifiers, including the numpad, which now works correctly. It’s still a bit rough around the edges, but I’ll try to get it up and running in the next few days
15 Likes
My TV has Chromecast. Is it possible to add a Cast-button on Youtube in this browser, like mainstream browsers have?
Fixed. Install updates and try again.
12 Likes
A big thanks!!! This also works on any GTK application around now 
Update on Geany comming up, now this is atleast usable being able to type characters as “#” 
1 Like
This fix (I hope) fully maps the Haiku keyboard layout to the xkb format used by Wayland. It also fixes the numpad (its behavior depends on the numlock state). An additional group has been added, enabled by pressing Opt with the Latin keyboard layout, so that hotkeys work with any layout (Alt+C, Alt+V, etc.).
13 Likes
Thanks, that was quick. @@@@@@@@@@@@@
The updated Wayland server works.
1 Like
Can’t say it’s working perfectly for me, though. The keymap is there, which is a great help, but periodically I have to foreground something else if I want to continue. Like, above when I typed “keymap”, it stalled at “key”; I selected something on the desktop and “map” came out.
Not just input - when I connected to this site, it got far enough on its own to change the title bar, and then I had to background it to wake it up. Back and forth between tabs, same problem.
I may be a little behind things at hrev 58867+, had to update nss separately if that means anything.
[edit]
Indeed, working better at 59048+. Keyboard input works fine with single input characters, not right with “dead keys” - of which I have ‘, `, ~, " and ^. Press ’, then press a, get ´á, where I should get just á - as in WebPositive, Terminal, StyleEdit. In other words, the dead key works, but it’s also a “live” key.
[/edit]
I notice not all emoticons work, in some forums. Is this possible to fix? 
They work in this forum, but it does not work on other forums.
Like this: 
They may just appear as a square with hex numbers inside.
I was able to solve this problem, but I need a few more days to test the behavior on different keyboard layouts.
9 Likes
Thanks man, everything works on my layout (my layout uses AltGr a lot). Now I can use gtk apps.
1 Like
This issue has been fixed in the latest update.
The latest release should also reduce CPU load due to the frame rate limitation during redrawing.
8 Likes
It may be just me, or not the right latest update - or there may be a general problem that affects everyone. I’m pasting ’ instead of typing it, because it is now a dead key on its own without the modifier. Where they should be normal ASCII single or double quote characters, which I now can´t type.
(In this respect I should have found the way to write, above, ‘Press <Option>' …’, which the Discuss input formatting makes awkward. Dead keys come to life, so to speak, with the Option key on my keyboard setting, where with no modifiers they’re the ordinary values on the key cap.)
On a separate note, I see that my ‘shortcut’ links now include one I didn’t ever visit, but rather is ‘sponsored’. This is a default ‘on’ option titled ‘Support Iceweasel’. Who does that support, I wonder - KENZ and 3dEyes at all, I hope?
[edit] It started out as one, an online travel aggregator, and then when I didn´t do anything about it, added a giant tennis shoe company. I turned it off. Settings>Home>Support Iceweasel. [/edit]
Work around for the single/double quotes, type them then hit space-bar, then they appear. (seen it too here), that worked before without the work around. Simular when you want to type “~” (that needs a default hit on the space-bar.
1 Like
Until recently, I had no experience with keymaps that had dead keys. Implementing their support in Wayland is complicated by this very fact. Explain in detail what’s wrong and how it should work, and I’ll try to fix it.
3 Likes
For now only the single/double quotes are giving issues here as explained above, no issue further at the moment. PS. Thanks for the work there!
1 Like
The following space technique works, “thanks!”.
I wish I really had a better idea how dead keys work. The Keymap preference utility and /bin/keymap keep this matter close to their chest, and frankly this morning I can’t figure out exactly how I got to the keymap I use - I have some home-made dead keys that I use for tilde and circumflex. But with the update they’re working fine.
The usual (default?) dead keys on US-International are
<option>+ ` (key 0x11): grave<option shift>+ ` (key 0x11): tilde<option>+ ’ (key 0x46): acute<option shift>+ ’ (key 0x46): diaeresis
And those are the keys that now don´t work correctly without the option modifier. They do work correctly with the option modifier, as do my home-made dead keys, so my guess is that very likely it’s just a matter of undoing one of the changes to this code.
Of course, these keys - 0x11 and 0x46 - should be ASCII in the US-International keymap, when pressed alone without modifiers. Three different quote characters and a tilde.
2 Likes
just curious, if you hit the ’ key, then follow it with a vogal( “a”, ‘e’, etc ) what is written in the screen ?