The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
It is not at all mandatory to use throws IOException. If you call a method that can throw an exception, though, you're required to either
ReplyDeleteCatch it, or
Declare that you're going to rethrow it.
The second one is what you're doing. The other one -- which is often the preferred technique -- is to catch and handle the exception yourself:
public static void main(String[] argv) {
try {
FileReader f = new FileReader("foo.txt");
// ... more
} catch (IOException ioe) {
System.out.println("Trouble reading from the file: " + ioe.getMessage());
}
}
AFAIK, it is not mandatory.
ReplyDeleteYou either handle the exception or you don't.
If you do handle the exception, then you need to put a try {...} catch(IOException e) {...}, but if you don't handle it, just declare the throws IOException in the current method.