same error with windows client...

ERROR 09-16 09:54:54.414 211 o.q.c.JobRunShell [CoreScreenShare_Worker-5] - Job ScreenShare.RemoteJob threw an unhandled Exception: java.lang.NoClassDefFoundError: Could not initialize class org.apache.openmeetings.screenshare.job.OmKeyEvent at org.apache.openmeetings.screenshare.job.RemoteJob.execute(RemoteJob.java:92)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ERROR 09-16 09:54:54.414 2425 o.q.c.ErrorLogger [CoreScreenShare_Worker-5] - Job (ScreenShare.RemoteJob threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception.
        at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.openmeetings.screenshare.job.OmKeyEvent at org.apache.openmeetings.screenshare.job.RemoteJob.execute(RemoteJob.java:92)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
        ... 1 common frames omitted

Am 16.09.2016 um 09:50 schrieb Peter Dähn:
Hi Maxim,

first test...

Linux to Linux nothing will be written right now...

Javaconsole gives following error

ERROR 09-16 09:40:51.412 211 o.q.c.JobRunShell
[CoreScreenShare_Worker-3] - Job ScreenShare.RemoteJob threw an
unhandled Exception:
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.openmeetings.screenshare.job.OmKeyEvent
    at
org.apache.openmeetings.screenshare.job.RemoteJob.execute(RemoteJob.java:92)

    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)

ERROR 09-16 09:40:51.413 2425 o.q.c.ErrorLogger
[CoreScreenShare_Worker-3] - Job (ScreenShare.RemoteJob threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception.
    at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
    at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)

Caused by: java.lang.NoClassDefFoundError: Could not initialize class
org.apache.openmeetings.screenshare.job.OmKeyEvent
    at
org.apache.openmeetings.screenshare.job.RemoteJob.execute(RemoteJob.java:92)

    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    ... 1 common frames omitted


with answer you question you mean input key and resulting char?

Windows tries remote write on linux...
öäüß´#+ gives #,8970



Am 16.09.2016 um 05:07 schrieb Maxim Solodovnik:
Commited: https://svn.apache.org/r1760990 Linux to Linux and Linux to Mac
remote should work as expected

On Thu, Sep 15, 2016 at 10:27 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

I will commit working code for Linux tomorrow

will appreciate if you can answer my question

On Thu, Sep 15, 2016 at 9:45 PM, Peter Dähn <da...@vcrp.de> wrote:

this is java console with linux client on both sites..

DEBUG 09-15 16:41:27.018 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-2] - sequence:: shift false, orig 246 -> key
246,
_key null, ch ö
DEBUG 09-15 16:41:27.202 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-6] - sequence:: shift false, orig 228 -> key
228,
_key null, ch ä
DEBUG 09-15 16:41:27.418 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-1] - sequence:: shift false, orig 252 -> key
252,
_key null, ch ü
DEBUG 09-15 16:41:27.685 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-6] - sequence:: shift false, orig 223 -> key
223,
_key null, ch ß
DEBUG 09-15 16:41:35.821 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-8] - sequence:: shift false, orig 51 -> key 51,
_key null, ch #
DEBUG 09-15 16:41:36.026 87 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-2] - sequence:: shift false, orig 187 -> key
61,
_key 61, ch +

the keys differ...


Am 15.09.2016 um 16:16 schrieb Peter Dähn:

Hi Maxim,

I neede a Windows Client on the other side...

now

öäüß´#+ gives #,8970

Debugmessages in Javaconsole

DEBUG 09-15 16:11:18.993 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-7] - sequence:: shift false, orig 192 -> key
192, _key null
DEBUG 09-15 16:11:19.322 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-3] - sequence:: shift false, orig 222 -> key
222, _key 222
DEBUG 09-15 16:11:19.689 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-1] - sequence:: shift false, orig 186 ->
key 59,
_key 59
DEBUG 09-15 16:11:20.100 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-9] - sequence:: shift false, orig 219 ->
key 91,
_key 91
DEBUG 09-15 16:11:20.917 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-5] - sequence:: shift false, orig 221 ->
key 93,
_key 93
DEBUG 09-15 16:11:21.687 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-1] - sequence:: shift false, orig 191 ->
key 47,
_key 47
DEBUG 09-15 16:11:22.016 83 o.a.o.s.j.OmKeyEvent
[CoreScreenShare_Worker-8] - sequence:: shift false, orig 187 ->
key 61,
_key 61

produce in OmKeyEvent.java line 85

Greetings Peter


Am 15.09.2016 um 15:51 schrieb Peter Dähn:

Hi Maxim,

I still try to use getExtendedKeyCode(). No luck till now...

By now I compiled the latest build. Nothing will be written on
öäüß´. It
has now all the same result like hitting ctrl+alt+s (my shortcut for
screenshots)???

Any ideas?


Am 15.09.2016 um 11:44 schrieb Maxim Solodovnik:

It seems like I have some progress .....
could you please tell me what is the expected behavior

1) to print on host character printed by client
2) to print key

the difference is keyboard layout of cause
imagine I have changed layout on client, and print Russian 'a', in
English
layout it will be 'f' .....

Why it is important: the only way I found to 'type' character is
https://en.wikipedia.org/wiki/Unicode_input
The alternative is to 'paste' character is very OS+application
specific
(for ex. on Ubuntu you need Ctrl+Shift+C to copy in Terminal,
Ctrl+C in
gedit ....)

On Wed, Sep 14, 2016 at 6:12 PM, Peter Dähn <da...@vcrp.de> wrote:

accidentally.... ;-)

Am 14.09.2016 um 13:08 schrieb Maxim Solodovnik:

OmKeyEvent is the transformer from what was received in FlashPlayer
to key
sequence for Java Robot
I'm also playing with it
accidentally was able to type ß, now trying to find out how :)

On Wed, Sep 14, 2016 at 6:00 PM, Peter Dähn <da...@vcrp.de> wrote:

I try to understand OmKeyEvent.java... If there is a place to fix
this it

must be there... right?


Am 14.09.2016 um 12:31 schrieb Maxim Solodovnik:

sort of :(

I can find no way to "type" these ExtendedKey
additionally it will be required to find out it need to be
pressed, I
mean
flash and/or Java need some way to understand it's time to press
umlauts
...
here is "sort of" solution
http://stackoverflow.com/questions/397113/how-to-make-the-
java-awt-robot-type-unicode-characters-is-it-possible
but I don't really like it ....

On Wed, Sep 14, 2016 at 5:24 PM, Peter Dähn <da...@vcrp.de>
wrote:

something like tis?

http://stackoverflow.com/questions/27680924/keycode-for-the-
key-%C3%9F





Am 14.09.2016 um 12:20 schrieb Maxim Solodovnik (JIRA):

        [
https://issues.apache.org/jira/browse/OPENMEETINGS-1468?page

=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=15490063#comment-15490063 ]

Maxim Solodovnik commented on OPENMEETINGS-1468:
------------------------------------------------

It is something outstanding :)
works for english and russian, but not for german :(
will try to understand what is going on

problems with keyborad usage while screensharing with remote
desktop

------------------------------------------------------------
---------


                    Key: OPENMEETINGS-1468
                    URL: https://issues.apache.org/jira
/browse/OPENMEETINGS-1468
                Project: Openmeetings
             Issue Type: Bug
             Components: Screen-sharing
       Affects Versions: 3.1.2, 3.1.3, 3.1.4
               Reporter: Peter Dähn
               Assignee: Maxim Solodovnik
                Fix For: 3.1.3, 3.2.0


During screen sharing with remote desktop one could use
all keys
except 3, german umlauts and ", - # + * ' _ ;"
This is the behaviour with Linux client with Open JDK.
Need to
test
also
Oracle Java.
But Windows also seem the have some unexpected behaviours.
After the
first time of using shift for capital letters one need to use
caps
lock for
writing capital letters.


--

This message was sent by Atlassian JIRA
(v6.3.4#6332)






--
WBR
Maxim aka solomax




Reply via email to