Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Digi

Pages: [1] 2 3 ... 6
1
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 04:24:41 am »
How about an OS/2 or ARCOS without Windows and DOS? Wouldn't that be easier?

I think that DOS (and Win-OS2) should have been thrown out of the system many years ago. :-)

2
Quick test - I works :-)

Not much time for extensive test, but €@²³µ work now. Thanks.

Excellent! Thank you.

3
I've now checked with xkbev which key codes is received. On the local keyboard AltGr produces keycode 108. When connected via ofreerdp the same key on the remote keyboard produces 2 keycodes - 37 and 64. Which probably is Ctrl and Alt. And this does not work. There are more differences but this one is the biggest problem.

Connecting the Linux box from Win10 instead OS/2 the Win AltGr produces keypress 37, keyrelease 37, keypress 113 and keyrelease 113.

So either our ofreerdp should send
1) keypress 108 when pressing AltGr and keyrelease 108 when releasing AltGr (in the meantime the other keys are should sent as usual) to mimik local behaviour or
2) keypress 37, keyrelase 37, keypress 113, keyrelease 113 to mimik Win behaviour. But Win make autorepeat of this sequence as long as AltGr is pressed. So option 1) like local keyboard maybe better

Have to say I'm no expert on this. But working combinations are -
- Win to Linux
- OS/2 to Win
non AltGr working is with -
- OS/2 to Linux

Also /kbd: options seems to do nothing (not implemented?) on our OS/2 client (ofreerdp.exe) as it always shows the usage messages. But this can be overcome with xrdp.ini and xrdp_keyboard.ini entries (force DE with override instead default to EN).

As I understand it, the codes in your post are codes for X11. According to this: https://github.com/sulmone/X11/blob/master/share/X11/xkb/keycodes/xfree86 , your option 2 is AltGr -> LCTL + RALT. But that's exactly what OS/2 freerdp does now. However, I found that Right Alt can be sent to the RDP server with two different scan codes.  :o

Please check this: http://os2.snc.ru/pub/freerdp/test/freerdp-wpi-20250217.zip
here I use a different scancode for Right Alt to send AltGr -> Left Ctrl + Right Alt.

PS: I don't understand which key corresponds to code 108.

4
With Win10 it works as expected. Seems some setting in X11 / xrdp?

Hmm... Looks like it.
To be completely sure, it remains to check the Linux freerdp client to Debian. :)

5
IBut none of the 3th keys work when I connect to a Linux/Debian box. I tried @ € ² ³ ~ tried. Currently I've no /kbd option on command line. Should I try again with /kbd:de,lang:de? My notes says this does not work in the past.

I start with (user/password changed to xxxx) -
Code: [Select]
ofreerdp.exe /u:xxx /p:xxx /w:2100 /h:1600  /v:m92p

I can't remember exactly what /kbd affects right now, I think we'll try without it for now (but of course nothing stops you from trying  :) ).

Now I thought - maybe I should send Left Ctrl + Left Alt instead of Left Ctrl + AltGr. If so, you should be able to type "@" by pressing Left Ctrl + Left Alt + q. Try it (but I doubt it).

It would be very interesting to know if AltGr works now on German systems when connecting ofreerdp to Windows...

6
Hi

Still not working is <Alt Gr> <e> EURO character and even worse @ (Alt Gr + q). Or better said I've not found a way to insert these. The way with <Alt> + number keys don't work too. No clue if this is a general limitation of rdp or some setting or....

I see my old comment in the source code:

  /* Support for the AltGr key on a German keyboard
     (Request from Herwig Bauernfeind). */

Then the following scheme is executed: 1. The current country for OS/2 is recognized. 2. If it is Germany (code 49) and the Right Alt (AltGr) key is pressed, then the remote system is sent a press of two keys: Left Ctrl and Right Alt (AltGr).

I think it worked then because that part of the code hadn't changed for a very long time. Could you (or somebody from German here) verify that it doesn't work if you connect to Windows?

And please try the following (it doesn't matter whether it's with Linux or Windows): take this test version:

http://os2.snc.ru/pub/freerdp/test/freerdp-wpi-20250214.zip

Connect to the remote system, press and release the AltGr key, and look at the console. If everything is ok, you should see lines like this:

!TEST! country: 49, codepage: 850
!TEST! Right Alt (pressed) -> Ctrl (0x1D) + Right Alt
!TEST! Right Alt (released) -> Ctrl (0x1D) + Right Alt

If you only see the first line with a different country code, please let me know.

7
Web applications / Re: Dooble releases, Qt5 builds
« on: December 19, 2024, 10:56:23 pm »
I was able to choose a font that made the text visible. Now configured:
  Sans Serif: Droid Serif
But with most of the fonts I choose the text becomes invisible.

Now there is a new problem - I can't enter text in my language in the address bar and in forms on websites. Only English works. The text is not being entered, this is not due to the fact that it is invisible.

8
Web applications / Re: Dooble releases, Qt5 builds
« on: December 19, 2024, 10:24:41 pm »
Have you tried moving the profile out of the way? It is in %HOME%\.dooble. Other then that and trying different fonts, I don't have any ideas.

I tried this, it doesn't help.

What do you have under [tools] - [Inject custom style sheet] ?

See attachment.

9
Web applications / Re: Dooble releases, Qt5 builds
« on: December 18, 2024, 02:19:50 pm »
Is it a font issue or a text color issue ?
White on white is not visible !

The problem is in the fonts, not in the color.

Did you empty Dooble cache to not reload cache pages but site pages ?

This does not help. The situation is reproduced on any sites, regardless of whether I visited them or loaded new ones.

10
Web applications / Re: Dooble releases, Qt5 builds
« on: December 18, 2024, 11:01:53 am »
That should have been "fc-scan -b X:/PSFONTS/TNR.PFB"

C:\>fc-scan -b c:/PSFONTS/TNR.PFB
Pattern has 18 elts (size 32)
        family: "Times New Roman"(w) "Times New Roman "(s)
        style: "Regular"(s)
        stylelang: "en"(s) "en"(s)
        slant: 0(i)(s)
        weight: 80(f)(s)
        width: 100(f)(s)
        foundry: "ibm"(s)
        file: "c:/PSFONTS/TNR.PFB"(s)
        index: 0(i)(s)
        outline: True(s)
        scalable: True(s)
        fontversion: 0(i)(s)
        fontformat: "Type 1"(s)
        decorative: False(s)
        postscriptname: "TimesNewRoman"(s)
        color: False(s)
        symbol: False(s)
        variable: False(s)

It's strange, but on my other machine I see the same result and there are no problems with fonts in dooble.

fc-cache -r

Nothing changed after that.

11
Web applications / Re: Dooble releases, Qt5 builds
« on: December 18, 2024, 04:19:28 am »
For some reason I can't see text on web pages.

12
General Discussion / Re: Resource Compiler - Joke
« on: October 26, 2024, 12:51:49 pm »
There are too few coders for OS/2 for this situation to be real.  :) And standardizing the resource compiler is a good idea.

13
Internet / Re: HTTPS server?
« on: October 05, 2024, 03:18:18 pm »
Sooo...what are our choices besides the Apache stuff?

You can take part in testing Manjary: http://os2.snc.ru/product-Manjary.html  ;)

14
Applications / Re: ANPM database error
« on: August 17, 2024, 04:50:48 am »
The netlabs repository and its mirror now work without problems on my systems.

15
Applications / Re: ANPM database error
« on: August 15, 2024, 12:09:47 am »
I see what you and David are talking about now - in ANPM your referring to the "available" files that you don't have installed - I also get 12 files listed - I was looking at the "installed" files, of which I have roughly 250 installed, and as of last week I could update them.

Once again, arcanoae-rel lacks many packages that are on netlabs-rel.

Pages: [1] 2 3 ... 6