Currently, consumers must use the monitoring method in order to retrieve the printer status, but consumers might want to use a one time status getter, which is not currently supported.
Some use cases for example:
Get status by demand (for performance or product reasons)
More control over every connection to the printer
More flexible monitoring options (not every X seconds, but in changing intervals or whenever the app is idle)
This contribution contains changes in the native code and a RN method addition, mainly leaning on the logic provided in the preformMonitoring methods (and also used by this method as well in the new implementation)
Currently, consumers must use the monitoring method in order to retrieve the printer status, but consumers might want to use a one time status getter, which is not currently supported.
Some use cases for example:
This contribution contains changes in the native code and a RN method addition, mainly leaning on the logic provided in the
preformMonitoring
methods (and also used by this method as well in the new implementation)