Sharing My Experience: How Screenshots Solved My Image Saving Problem

Sharing My Experience: How Screenshots Solved My Image Saving Problem

Here's one of the nice comments I received today.

This is a post I wrote about what happened when my child first drew a rose with me when he was five years old. I remember how difficult it was for him to draw a rose for the first time, and I documented that process.

​So, I wrote this very short and simple post, wondering how I could help a five-year-old understand and confidently draw the complex rose.

https://www.annakoh.com/blog/how-to-draw-a-rose-for-kids 

​This article, though short, was well-received because it was based on real-life experiences. However, after a recent comment, I went back to the previous page and discovered that several images had been replaced with incorrect ones, so I made corrections.

Clearly, it was a rose before, but I was surprised to suddenly see snow. And I feel sorry for visitors who might have thought it wasn't a rose. However, the fact that the image changed like this without my knowledge is due to a fatal flaw in Weebly.

https://www.annakoh.com/apps/search?q=overwriting

​The simplest way to avoid overwriting when saving images is to use screen capture. If you download images directly, you'll need to name them each time, and if you save them with the same name, the previous file will be overwritten by the new one. However, screen captures automatically generate file names, and they're usually numbered with the date and time of capture, preventing duplicate names. Therefore, using the capture method allows you to safely and continuously save images without file name conflicts.