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

WIP : PAPPL Scan API Integration #349

Draft
wants to merge 13 commits into
base: v1.4.x
Choose a base branch
from

Conversation

Kappuccino111
Copy link

Actively updating for solving #130, #131 , #133 , #134.

Copy link
Owner

@michaelrsweet michaelrsweet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't a complete implementation.

@Kappuccino111 Kappuccino111 changed the title PAPPL Scan API Integration WIP : PAPPL Scan API Integration Mar 23, 2024
@Kappuccino111
Copy link
Author

Kappuccino111 commented Mar 23, 2024

@michaelrsweet, the implementation is still a work in progress. All updates are regularly posted on the comments in #130

I have now pushed the scanner-accessors.c file. One doubt that I have is that papplSystemAddEvent() is pre-configured for printers, and hence passing a scanner object while using papplScannerResume() or papplScannerPause() creates warnings. Any ideas on how to proceed with this? For now, I am simply debugging to the terminal.

@Kappuccino111 Kappuccino111 marked this pull request as draft March 23, 2024 08:50
@michaelrsweet
Copy link
Owner

@michaelrsweet, the implementation is still a work in progress. All updates are regularly posted on the comments in #130

I have now pushed the scanner-accessors.c file. One doubt that I have is that papplSystemAddEvent() is pre-configured for printers, and hence passing a scanner object while using papplScannerResume() or papplScannerPause() creates warnings. Any ideas on how to proceed with this? For now, I am simply debugging to the terminal.

For now I would add a different version of papplSystemAddEvent that accepts the scanner pointer. Longer term we'll need to do something more coherent, of course, but for now a separate function will do just fine for a first implementation.

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.

None yet

2 participants