Given your (UCSC-formatted) BED file, you could use the ucsc-fetch script to make a folder of images containing UCSC Genome Browser shots. The track selection is based on a tracks file that describes what is shown and how it is shown (full, dense, etc.).
Once you have that folder of images, you could use a tool like SimpleViewer to make a gallery. You might use a Perl or Python script that makes the required XML-formatted gallery file (this describes how the gallery is constructed and what images go into it), copies images to the images subfolder, and uses ImageMagick to make thumbnails to copy to the thumbs subfolder.
Images in the resulting SimpleViewer gallery can be opened in a web browser and you can navigate through them with arrow keys or mouse-click events. It's a pretty slick bit of gear.
I use a variation of the above recipe to make plot galleries for internal use in our lab. I use an internally-written equivalent of ucsc-fetch that works with internal UCSC Genome Browser instances, and hooks into SimpleViewer Pro for some extra browser functionality - for example, to offer a link to internal Genome Browser instances at the image's equivalent BED coordinate range and browser session ID, to load specific tracks.
It works pretty great. For various reasons, I'm not sure we can release our internal ucsc-fetch equivalent to the public, but here's the Perl script I use to make a SimpleViewer-based gallery XML file and other resources from an input folder of images. The use of this Gist by others would need some local customization, but perhaps it can help save some time:
You'll need to install ImageMagick, have a folder containing SimpleViewer or SimpleViewer Pro resources available, and a Perl library installed called XML::Writer
to handle making the gallery XML file. But with an hour or two of coding and tweaking, the arrangement I describe above can be pretty easily repeated by others.
So pretty much the consensus of the answers seems to be: "No. You need to write a less or more complicated script to do this." with plenty of suggestions on how to do this below.
Behind every convenient technology, there are usually people sweating the details on your behalf, yes.
What exactly would have merited a "yes, there is a convenient way" in your opinion?
IMHO, running bedTools once and subsequently loading the script beats having to click "next" for x number of times, but I may have misunderstood your intention.