First a question. In the program included should I be expecting to not have Picture1 change immediately(on the screen running through VB versus compiled) after I press the mouse button. I think I've been through this discussion before. Does Picture1.PaintPicture take a while to process while the program will continue on with the rest of the code??? I keep noticing the long delay before the image changes and it just hit me that this might be the reason why.
After hitting the left mouse button the program brings up the 6 hour forecast image and it should start calculating the precip that is suppose to fall over each pixel of the map(works great) and then create a 6 hour forecast map that has had the isobar(black) and 540(red and blue) lines removed/smoothed out of the image(works great). Basically this is just a copy/smooth of the original 6 hour forecast map leading the way into the 12 hour forecast map. When it brings up the 12 hour forecast map it should now take the precip that was forecasted to fall in the first 6 hours and add it to the precip forecasted to fall in the next 6 hours to give the 12 hour accumulated precip(works great...kind of I think).
It appears to be doing it correctly except now when it redraws the new map the whole map image has shifted both down and to the right from where it was on the original 6 hour forecast or where it is on the original images to start with. It kinda looks like it has tried to increase the size of the image as the top and left hand side of the image is still in the same location. I see the right side of the image that normally is blank now is mostly map when it goes to image 2. After the initial move it doesn't move again it stay down and to the right of where it should be for image 3. I haven't carried it any further yet than image 3. I can't see any reason for this unwelcomed move in the code. I see the precip bar(far left side of the screen) even has some shifting, both downwards and very slightly to the right.
Why is this occuring. What have I did wrong that is making this happen. I've looked the code over numerous times trying to make sense of what I've did wrong and I don't see it.
Also, by any chance...is their a quicker way of accomplishing this? You have to be able compute from one map to the next what the total is and carry it forward, hence why I've went with the 2-D array to store the precip total for each pixel and hence why I've also just been doing it with Picture1.Point versus using BitBit. From what I've seen it sounds like BitBit wouldn't work under these circumstances for this kind of purpose...or am I wrong?
Reply With Quote