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

Fix 65 Use ⎕DQ rather than ⎕TGET #77

Merged
merged 11 commits into from
Dec 21, 2024
Merged

Fix 65 Use ⎕DQ rather than ⎕TGET #77

merged 11 commits into from
Dec 21, 2024

Conversation

mkromberg
Copy link
Collaborator

@mkromberg mkromberg commented Nov 29, 2024

For review only - do not merge.

In order to capture HTMLRenderer events, switch to using ⎕DQ rather than ⎕TGET to displatch incoming events from the web socket.

The "code" namespace already contains a Timer object called _EWC.TIMER, which was used to enable interactive DQ. In the new strategy, ∆DQ is always doing a ⎕DQ of that object, and instead of using TGET/TPUT to transfer events to ∆DQ, EWC.Handler ⎕NQ's a 1001 event to the TIMER, which calls the function dqTimer.

  • If we are in a ∆DQ, the event is re-enqueued as a 1002, which causes the ⎕DQ in ∆DQ to terminate so the event can be handled in that function.
  • If we are NOT in ∆DQ ("interactive mode"), dqTimer handles the event itself. This should possibly still be controlled by the NOIDQ switch.

@mkromberg mkromberg requested a review from cursork November 29, 2024 05:33
@cursork cursork merged commit 6871685 into main Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants