The good news is that you only need one meter to display it. The bad news is that you indeed will need 24 "child" measures to get each of the images from 0 to 23. Let me know if you still have questions, we are glad to help. More on how to use "relative paths" with WebParser is Here. NOW we can download that with Download=1 and it will be available for an image meter to display. What this is doing is adding the image name we captured in StringIndex 1 of the parent measure to the base URL so in effect what we end up with as the URL is:
So, we need some "child" measures to get the images down to us. The measure is just returning image names, not fully formed URL's to the images. We can't just stick Download=1 on that measure. So that measure,, will have two StringIndexes. *, so you could add the rest of the images using the same pattern. * until we hit map.FrameElement\ = " (again escaping the characters) until we again hit ". You are saying search for map.FrameElement\ = " (notice that we had to escape the characters with a "\" as they are reserved characters in Regular Expression) then capture everything until we hit " Then skip all characters with. I have done just the first two, so you can see how to do it. So in the parent WebParser measure,, we want to collect all the image names from that page.
0 kommentar(er)
