Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

$ZA and $ZB variables are not changing in WebTerminal #92

Open
nikitaeverywhere opened this issue Feb 7, 2017 · 0 comments
Open

$ZA and $ZB variables are not changing in WebTerminal #92

nikitaeverywhere opened this issue Feb 7, 2017 · 0 comments

Comments

@nikitaeverywhere
Copy link
Member

nikitaeverywhere commented Feb 7, 2017

Issues #81 and #87 and possibly #77 are related.

These special variables are not changing (or change incorrectly) in WebTerminal: $ZA $ZB. See the related issues to get more information.

Once this issue gets solved, it would be possible to fix related issues.

Any ideas of how to change $ZA or $ZB variables programmatically are appreciated.

In brief, technically, WebTerminal session is handled by 2 Caché processes, one handles WebSocket connections, and the other (core) handles commands execution and lasts for all the time until client closes the session. These two processes use inter-process communication (IPC) to exchange data. WebSocket process sends data to core process using Caché IPC. The task here is to handle this data in a way that enables to set/change/whatever $ZA and $ZB special variables, as they are the main variables which client applications read to determine which key(s) were pressed. E.g. when escape sequence, for example, ^[OP comes to the server it should properly set $ZA and $ZB. Currently this values does not change at all.

P.S. Here is the code of how the transmitted data (lets say any data client can send) appears in core process.

You can contact me directly if you know the solution, many thanks on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant