Timeline for Image-resizing methods
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2012 at 0:02 | vote | accept | kentcdodds | ||
| Apr 26, 2012 at 19:06 | comment | added | Konrad Rudolph | Now I agree: for this case, it’s overkill. | |
| Apr 26, 2012 at 19:05 | comment | added | Quentin Pradet | Reworded my answer. | |
| Apr 26, 2012 at 19:03 | history | edited | Quentin Pradet | CC BY-SA 3.0 |
updated.
|
| Apr 26, 2012 at 16:11 | comment | added | Konrad Rudolph |
That’s wrong. Graphics2D is about painting on an image. It is not in any way about "displaying" images. It just so happens that most UI widgets manage their own drawing object rather than just the underlying buffered image (For performance reasons I imagine). That said, the new code doesn’t have any advantage over the old code in this particular instance. But as soon as you need to actually draw, use a Graphics2D object.
|
|
| Apr 26, 2012 at 13:20 | history | answered | Quentin Pradet | CC BY-SA 3.0 |