every weak 4 images comes,

[82rathi.angara]

Actually i want to display images in my application. So every weak 4 images comes ,weak wise images change. So give me logic or code in java .

[Norm]

You'll have to show your code for anyone to be able to suggest how to change it to show the new images.
One solution would be to list the images to be shown in a file and have the app read the file to get the names of the images to be shown.

[82rathi.angara]

You'll have to show your code for anyone to be able to suggest how to change it to show the new images.
One solution would be to list the images to be shown in a file and have the app read the file to get the names of the images to be shown.

but how to get it week wise.After each 7 day images change.

[Eranga]

Use a swing timer to change image. Set the timer to 7 days and load the image into the required place.

[Supamagier]

Or use a thread, or just use date, it all works. You should google for the 'correct' code.

[Eranga]

Ya, lots of choices there, depends on the implementation choose the best.

[Supamagier]

For once every seven days I would choose to compare the date every now and then. ;) I think that would be best - least memory-consuming, but I may be wrong, correct me if so. :)

[Norm]

So every weak 4 images comes

How does the program access the images? Are they in a folder with all the previous images? What controls where the new images are placed?

[Eranga]

For once every seven days I would choose to compare the date every now and then. ;) I think that would be best - least memory-consuming, but I may be wrong, correct me if so. :)

So you may use a thread there. Basically you have to keep track of seven days anyhow, throw a thread or anything. Memory managements are based on your implementations. Actually Java done the most of it for you.

[Supamagier]

True, I just thought of the fact that you had to check it every now and then, and needed a timer for that anyways, so, indeed, it doesn't really matter what you use, although I prefer Threads.

[Eranga]

I think so, threads are much safer. But if you are dealing with in GUI implementation swing timer could be better too.

[fishtoprecords]

Normal good design practice is to set a thread with a wakeup (sleep()) time that wakes up before your deadline. Wake up, see if the deadline has passed, if not sleep for 75% more.

This way, if your code dies or if the timers are off a bit, you can be safe.

This is also a good time to check that your computer is using a NTP pool server for time.