SDK/J

Support

We are very close to a final build and just need to ensure the complete xlet removes all threads when it is destroyed.

I have seen intermittently an error when removing and re-deploying our xlet.  There is a null pointer exception raised occasionally when we start our xlet if the device hasn't had a reboot after redeployment.

I want to ensure this is fixed or isn't a problem before we submit this xlet for testing.

How should the Operation Panel be unsubscribed to once the xlet isdestroyed?

The following are the methods to initialise ad remove the listeners within the MainWindow:

These are class scope (MainWindow):

private OperationPanel devicePanel;
private KeyAdapter keyAdapter;

public void initKeyEvents() {

        this.devicePanel = OperationPanel.getInstance();

        this.devicePanel.addKeyListener(keyAdapter = new KeyAdapter() {        

            public void keyPressed(KeyEvent ke) {

                if (loginContext != null) {

                    switch (ke.getKeyCode()) {
                    case KeyEvent.KEY_LOGIN_OUT:                    
                        if (!Session.isQuotaExceded) {
                            if (loginContext.isLogin()) {
                                setApplicationFocus();
                                logout();
                            }
                        }
                        break;
                    case KeyEvent.KEY_DUMMY:                   
                        if (loginContext.isLogin()) {
                            if (!Session.isQuotaExceded) {
                                resetTimer(120);
                            }
                        }
                        break;
                    }
                }
            }
        });
    }

public void dispose() {     

        this.devicePanel.removeKeyListener(keyAdapter);    
        keyAdapter = null;
        super.dispose();
    }
 

Everything functions perfectly but I am aware that this could cause a problem in testing if the OperationPanel thread is throwing an exception when we launch the application and don't reboot the device,

Please advise how this should be handled and changes based on the above code.

many thanks and best regards

Nick

Hi Support,

We have a requirement to launch our Pull Print application form the browser. I understand that Nick Parker has a resolution for 11x and 12x platforms by creating an Xlet that can launch the browser and select the book mark. We need a more elegant solution for a 10x platform.

Can you please advise if there is any way to perhaps create a new icon on the home page that will launch the browser to it's home page. Is there a way to customize the Icon and Icon name to something like ROI Pull Print?

Thanks,

Hi,

We have a new version of ScanPrefix that we need to certificate on CVM 11. The process remains as always? In this ticket we attach the different documents? (Manuals, Purchase Order And Contract, etc).

Can you tell me aprox how much time will take?

Regards,

Emiliano

We have performed our QA on the application and are ready to submit it to you for approval.  We will be sending out the VM's on Monday.  If there is anything else you need from me please let me know.  

The application consists of 2 applications a servlet and a xlet.  I have included an unsiged version of them both which includes their DALP files.

Support links:

Guys,

We really need some assistance here as we are banging our heads against a brick wall!

We have purchased a card reader which I know is supported and I have installed your test Xlet (usb card reader test). When I launch the test Xlet and present a card to the reader we get the exact same data stream from your Xlet that we are getting from ours (see other ticket number - #964- interpreting the card reader stream).

We are using a PCProxPlus card reader (RFideas) with the following information:

RDR - 80081AKU with the vendor ID in the attached screen shot. The stream is the same as the string in the #964 ticket.

The manual that you sent to Nick Parker to program the card reader is an old manual which doesn't cover the new reader. I have downloaded the correct manual and config tool and gone through the entire process of programming the reader with the card . I have also checked the bytes that the card is generating from the tool, converted it and it shows the correct card number (23499).

I don't know what else to try here as I have plugged in the card reader to another vendors device and it works perfectly with our software! I can log into the device by swiping the same card to the same reader and it works.

Can you PLEASE tell us how to get the correct number for the card from the Ricoh API as we are unsure if the problem is a configuration problem on the device, the Ricoh API or something that we need to do.

Both your test Xlet and our's are both getting the same results which is strange! Please tell us how to get the software to output the card data correctly or how to convert the output into something which matches the card number.

This is a priority now as this is holding up our project and we need to get this resolved asap.

If we could even get on a call to discuss this issue and hopefully find a resolution that would be great!

Thanks,

Hi support

I have received a stream from the usb device when a card is presented but I am struggling to resolve this to the actual card number.

The card number is : 23499 when presented and received in the tool shipped with the reader.

The reader is a RF IDeas pcprox plus.

What I receive inside the xlet is the following string from the bytes sent:

000000000000000000002000
000000000000000000000000
000021000000000000000000
000000000000260000000000
000000000000000000002600
000000000000000000000000
000028000000000000000000
000000000000000000000000

What I am unsure of is what this string represents as there appear to be 192 bytes of data returned and I am also unsure what base these bytes are sent in HEX , Decimal? as I need to achieve 23499 from them.

Any info greatly appreciated..

Best regards

Nick

Support

We have encountered a major issue with duplex copying which behaves exactly the same on both devices we have:

SP4510SF

MPC306Z

Every time a duplex copy event is raised it is followed by a simplex.event.

We have tested this over and over on both devices and the result is the same.

4 single sided pages to 2 duplex pages is exactly what we get out of the device but we get 4 events raised as follows:

     1 duplex mono

     1 simplex mono

     1 duplex mono

     1 simplex mono

What we should have/expect to received is:

     1 duplex mono

     1 duplex mono

We are receiving the events directly from the listener and whilst I can code around this Api shortfall it is wrong and doesn't function correctly based on what was copied.

Please can you look into this as a matter of urgency.

Many thanks

Nick

Hi Alex,

We send to version 5.3.1 of the NDDPrint for maintenance signature.

- Panels Supported: WVGA, uWVGA;

- Plataforms supported: 7x,10x,11x and 12x;

Release Notes:

• Correction when rounding the calculation of duplex/mono conversion values of documents
• The text "CORPORATE" was removed from the CORPORATE button in the Finality of Work screen, leaving only the icon to identify it;
• Changes in resources, some messages were bigger than the panel size and were being cut.

Kind Regards,

Anderson Palhano

Support

Whilst panel locking/unlocking functions perfectly under a normal session condition, the panel fails to unlock when the device returns from sleep mode and a user logs in.

I have used the example lock/unlock panel from the documentation.  Has this issue ever been reported before?

If you have any info or work arounds for this problem please let me know.

Best regards

Nick

Support

Can you point me at the documentation and examples to achieve usb card authentication.

I have as far as I am aware got the Usb listener and manager initialised and started which shows the attached device in cygwin.

The problem is no card number is received inside the xlet when a card is presented to the reader.  I do not have the card reader model number but it was recommended by Joe Gormley so is definitely a compatible reader.

ONESHOT_MODULE is implemented for remote authentication but I am obviously missing something.

Any samples greatly appreciated as I can check if I have missing methods or anything I haven't declared etc.

Best regards

Nick