ramonlopes / jzebra

Automatically exported from code.google.com/p/jzebra
0 stars 0 forks source link

removing the printer after jzebra applet is loaded #120

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Load the applet
2. Load all printers
3. delete 1 printer after applet is loaded
4. deleted printer is still there. 

What is the expected output? What do you see instead?
  I see that the existing printer is still there even if I delete the printer in windows. 

What version of the product are you using? On what operating system?
  I use 1.4.5 in windows 7, using firefox browser 19.0.2

Please provide any additional information below.

Original issue reported on code.google.com by frendca...@gmail.com on 20 Mar 2013 at 4:33

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
You will need to fully refresh the page (may require you to restart the 
browser, or restart the browser tab if in Chrome) for the printer listing to 
reflect that of Windows.  This has been the behavior since the beginning.  I'll 
leave this bug open as an enhancement request in the event JVM permits altering 
this behavior.

Original comment by tres.fin...@gmail.com on 20 Mar 2013 at 5:25

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
SIMILAR PROBLEM - JZEBRA WONT ERROR ON UNSUCCESSFUL FIND IF A SUCCESSFUL FIND 
HAS ONCE OCCURRED

If a printer has already been selected, and then it's searched for again and 
returns null, the applet keeps the old printer name.

I came across this today after asking the applet to search for a new printer.  
If it's the first unsuccessful search, it displays the correct error. However, 
if it found a printer previous to searching, it won't error, and always 
displays the last used printer.

Since it's a problem with the way the applet is caching the printers, I'm going 
to mark this bug as a defect, accepted and group both issues into one.

Thanks for this bug report.

-Tres

Original comment by tres.fin...@gmail.com on 26 Mar 2013 at 4:00