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

After doing some more tests i come to conclusion that from the moment you see the pdf on the screen and then close it immediately it take sometimes 10 seconds before it executes the next statement, when i leave the pdf a few seconds open on the screen and then close it the next statement will be executed almost immediately ! #4821

Open
dany060954 opened this issue Feb 27, 2025 · 1 comment

Comments

@dany060954
Copy link

After doing some more tests i come to conclusion that from the moment you see the pdf on the screen and then close it immediately it take sometimes 10 seconds before it executes the next statement, when i leave the pdf a few seconds open on the screen and then close it the next statement will be executed almost immediately !

Originally posted by @dany060954 in #4820 (comment)

@GitHubRulesOK
Copy link
Collaborator

GitHubRulesOK commented Feb 27, 2025

No as shown in other question SumatraPDF will run the second command in sequence potentially even before the first has completed all its renderings. The problems you encounter are using a shell rather than direct use of the control channel that SumatraPDF itself uses. Internally once loaded RESIDENT it uses piped DDE commands from user keyboard or 3rd party application or others from the shell which may have its own problem handlers.

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

No branches or pull requests

2 participants