Ya, and I couldn't frankenbuild it either.
I am eager to take a peek though.
Oh, and I've got a good tip that's slightly related to the .sln file.
Sometimes that file ends up inside the folder along with the .vbproj file, after converting from an older solution 2003.
It's easy to move the .sln to it's proper placement outside.
Then open it with notepad, and on the 3rd line or so, you can modify the path to the .vbproj file.
The solution file is getting an error, saying that it was created by a newer version. Perhaps 2010?
The project file seems to open fine though.
But man, this 2008 makes everything run wicked slow.
I had tried 2008 early last year, and gave up because of the insistently annoying intellisense, and extra junk jazz that was pre-requisite.
I'm beginning to regret re-installing it, but I got check it out more thouroughly I guess.
Unforetuneatly, 2008 has got to go for now.
It's causing all of my windows a 400-800 millisecond delay before showing.
I mean all of them.
I'm gonna re-re-install it after doing a 2 minute shutdown, and see what happens on my other machine too.
If nada, then it gets the boot for good.
Last edited by TT(n); January 15th, 2009 at 02:53 AM.
The basic idea about not zooming the mask image is taken from work done in the Crop/ Zoom project Thread, (VB6 forum)..
This way you have a lot less distortion of the pixel data, and a more accurate Hotspot definition.. (If the zones are painted properly..)
In the Grey scale image i just used a 20 pixel pen to paint over the specified hotspot regions, Freehand.. then i saved it in Jpg format, that does haze the edges, BMP is better for masks..
I also used a 10 step color gaps as it alows you to see the different regions in the mask, however you can use 1 step color gaps, and have 255 hotspots... or you could use truecolour and have prety much unlimited hotspots..
I'm not sure why it told you that it was created in a newer ver.. I'm using VS 2008 Pro.. (9.0.21022.8)
It's super impressive, and very short code. I was expecting at least 3-4 pages.
I had a hard time trying to trick it into giving the wrong hotspot at all.
You're right, it should not have thrown that error, because my version in the about window, says 9.0.30729.1, which is actually newer than yours.
However, I suspect it's the pro or Studio, since this is only express. Not sure how that works though.
Last edited by TT(n); January 15th, 2009 at 03:52 AM.
Because Pic2 is a background mask, and the user does not get to see it, i used all the greyscale bits, giving me 256 different regions. (&H00 - &HFF) ..
I used white (&HFF) as the base region, or background, non hotspot. and painted each region needed as a hotspot with a different color.
So for the first region i used black (&H00).. For region 2, I could have used the next color (&H01) but i jumped a few to visually show the different regions in the masked image. So region 2 is color 10 (&H0A), region 3 = 20 (&H14) .. etc
Esentually you use each available color as a region, and can have 255 hotspot regions set in the image.
Last edited by GremlinSA; January 16th, 2009 at 01:33 AM.
That is a clean and usually better approach....but, the original post:
based on a picture
Technically eliminated any approach where 2 images (one for display one for mask) was used.
Once one "plays with" the two image approach and is comfortable in understanding its operation, it should not be difficult to make the jump to slight restrictions in the image colors. e.g. only even shades so that the least significant bit is not used to convey color, but rather conveys (part of) the mask.
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009 In theory, there is no difference between theory and paractice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first