bidi error

Question

I have a metro app in which I have a device( printer) associated with the app via its device meta data. I can enumerate the associated printers and display in app. Then I try to get the ink level of the device using bidi query. But the bidi query returns error code 13005. I did some googling and found that not much info is around regarding this error. I am requesting the ink level as \\Printer.Consumables". What could be the reason? The app is from the metro sample collection "Device app for printers SDK sample"(http://code.msdn.microsoft.com/windowsapps/Device-app-for-printers-91f363a9 )

Answer 1

Where can I get detailed info about bidi query and sending bidi query to device.

I tried to get ink level from a device connected and enumerated via the Metro style device app downloaded from windows metro  samples collection. When I did so , I got an error 13005 from the bidi response though the bidi query is successful. The device is correctly associated with the app, I believe. What could be the reason?  Is there anything more I should do to get the ink level from bidi query?

Answer 2

I am aware that if a Metro style device app has registered for the Print Task Settings option, then printer status like low ink, out of paper will be notified to the app via Bidi communication and toast notification. My question is will all the statuses of a printer like low ink , etc be automatically notified to the app or should the app send bidi query to get each status separately?

Also , MSDN says that some printer statuses will be notified only when it is printing. Can we explicitly send a Bidi query and get the status via the app  without having the printer notify the status, no matter whether it is printing or not?

Answer 3

Hi its me here,

This is not something we can answer in the forums. If you need help with this please open a support case at http://getsupport.microsoft.com

--Rob

Answer 4

Thank you Rob for the reply. But may I please know why this cannot be answered in a forum? This was based on the white paper on developing device apps..