|
|
You're in the
dotnet compact framework
group:Two different argb values...
dotnet compact framework:
the same version of OS and both are PPC2003. When I do the following: 1) I load the same image on both PPC displays 2) Get a pixel color 3) use the pixel.toargb() function I get two different results. Why is this? Should they not be the same value? ------------------------------------------ Noble D. Bell AgForest Partners, Inc.
It depends on a screen color depth. If you see some LSBs are set to zero,
you might have 16 bit video on one device and 12 bit video on another. It also might be 5:5:5 vs. 5:6:5 format difference. -- Best regards, Ilya This posting is provided "AS IS" with no warranties, and confers no rights. *** Want to find answers instantly? Here's how... *** 1. Go to http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en 2. Type your question in the text box near "Search this group" button. 3. Hit "Search this group" button. 4. Read answer(s). [quoted text, click to view] "Noble Bell" <NobleBell@discussions.microsoft.com> wrote in message news:B4573654-8957-46A0-A512-CDF690F506CF@microsoft.com... >I have to different PPC's by two different manufacturers. Both are running > the same version of OS and both are PPC2003. > > When I do the following: > 1) I load the same image on both PPC displays > 2) Get a pixel color > 3) use the pixel.toargb() function > > I get two different results. Why is this? Should they not be the same > value? > > > ------------------------------------------ > Noble D. Bell > AgForest Partners, Inc. >
Hmm...
Thats interesting. If that is the case then how would one ever take the argb value of a pixel and look it up in a database table against a list of values if the pixel argb value could be different on different hand helds? What is the norm on ppc's for color depth nowadays? 16-bit? 32-bit? nb ------------------------------------------ Noble D. Bell AgForest Partners, Inc. [quoted text, click to view] "Ilya Tumanov [MS]" wrote:
> It depends on a screen color depth. If you see some LSBs are set to zero, > you might have 16 bit video on one device and 12 bit video on another. > > It also might be 5:5:5 vs. 5:6:5 format difference. > > > -- > Best regards, > > > Ilya > > This posting is provided "AS IS" with no warranties, and confers no rights. > > *** Want to find answers instantly? Here's how... *** > > 1. Go to > http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en > 2. Type your question in the text box near "Search this group" button. > 3. Hit "Search this group" button. > 4. Read answer(s). > > "Noble Bell" <NobleBell@discussions.microsoft.com> wrote in message > news:B4573654-8957-46A0-A512-CDF690F506CF@microsoft.com... > >I have to different PPC's by two different manufacturers. Both are running > > the same version of OS and both are PPC2003. > > > > When I do the following: > > 1) I load the same image on both PPC displays > > 2) Get a pixel color > > 3) use the pixel.toargb() function > > > > I get two different results. Why is this? Should they not be the same > > value? > > > > > > ------------------------------------------ > > Noble D. Bell > > AgForest Partners, Inc. > > > >
It is a colormap. What we are doing is that we have 4 states on a display and the user can tap on any one of the 4 states and it will take them to another screen that has a series of farm fields, the user again taps on a selection until he gets the one that he wants to work with. The only way that I could achieve the user being able to tap on any area in the polygon and get the right image was to make a color map and overlay the original image over the top of it. In other words the user sees the states image but when the user taps the ppc gets the location of where the user taps and the pixel color from the underlying colormap of RGB colors. The RGB color is turned into an argb color value that has references in a database table to tell the program what the user clicked. Kinda hard to explain but I think you might get the idea. I am very open to an easier way to achieve this if anyone has one. Thanks everyone for helping me. I really appreciate it. ------------------------------------------ Noble D. Bell AgForest Partners, Inc. [quoted text, click to view] "<ctacke/>" wrote:
> > Thats interesting. If that is the case then how would one ever take the > > argb > > value of a pixel and look it up in a database table against a list of > > values > > if the pixel argb value could be different on different hand helds? > > I've got no idea why you'd want to look it up in a database, but you can > always strip the LSBs and do a lowest-common-denominator comparison. > > > > > What is the norm on ppc's for color depth nowadays? 16-bit? 32-bit? > > > > There is no "norm". 12 and 16 bit are the most common. It's unusual to see > more depth, as most displays of the size you're looking at don't support any > higher depth, so it's just a wast of memory and bus bandwidth. > > -Chris > >
[quoted text, click to view]
> Thats interesting. If that is the case then how would one ever take the > argb > value of a pixel and look it up in a database table against a list of > values > if the pixel argb value could be different on different hand helds? I've got no idea why you'd want to look it up in a database, but you can always strip the LSBs and do a lowest-common-denominator comparison. [quoted text, click to view] > > What is the norm on ppc's for color depth nowadays? 16-bit? 32-bit? > There is no "norm". 12 and 16 bit are the most common. It's unusual to see more depth, as most displays of the size you're looking at don't support any higher depth, so it's just a wast of memory and bus bandwidth. -Chris
Wouldn't it make more sense to figure out where he tapped by looking
at...well, where he tapped? Rather than what color pixel he tapped on? Paul T. [quoted text, click to view] "Noble Bell" <NobleBell@discussions.microsoft.com> wrote in message news:7093CFE1-9689-4751-ABAA-36C40B58836B@microsoft.com... > > It is a colormap. What we are doing is that we have 4 states on a display > and the user can tap on any one of the 4 states and it will take them to > another screen that has a series of farm fields, the user again taps on a > selection until he gets the one that he wants to work with. > > The only way that I could achieve the user being able to tap on any area > in > the polygon and get the right image was to make a color map and overlay > the > original image over the top of it. > > In other words the user sees the states image but when the user taps the > ppc > gets the location of where the user taps and the pixel color from the > underlying colormap of RGB colors. The RGB color is turned into an argb > color > value that has references in a database table to tell the program what the > user clicked. > > Kinda hard to explain but I think you might get the idea. I am very open > to > an easier way to achieve this if anyone has one. > > Thanks everyone for helping me. I really appreciate it. > > ------------------------------------------ > Noble D. Bell > AgForest Partners, Inc. > > > > "<ctacke/>" wrote: > >> > Thats interesting. If that is the case then how would one ever take the >> > argb >> > value of a pixel and look it up in a database table against a list of >> > values >> > if the pixel argb value could be different on different hand helds? >> >> I've got no idea why you'd want to look it up in a database, but you can >> always strip the LSBs and do a lowest-common-denominator comparison. >> >> > >> > What is the norm on ppc's for color depth nowadays? 16-bit? 32-bit? >> > >> >> There is no "norm". 12 and 16 bit are the most common. It's unusual to >> see >> more depth, as most displays of the size you're looking at don't support >> any >> higher depth, so it's just a wast of memory and bus bandwidth. >> >> -Chris >> >> >>
I think Noble means a color map like what game programmers sometimes use for
collision detection. I had a similar problem a while ago. [quoted text, click to view] "Paul G. Tobey [eMVP]" wrote:
> Wouldn't it make more sense to figure out where he tapped by looking > at...well, where he tapped? Rather than what color pixel he tapped on? > > Paul T. > > "Noble Bell" <NobleBell@discussions.microsoft.com> wrote in message > news:7093CFE1-9689-4751-ABAA-36C40B58836B@microsoft.com... > > > > It is a colormap. What we are doing is that we have 4 states on a display > > and the user can tap on any one of the 4 states and it will take them to > > another screen that has a series of farm fields, the user again taps on a > > selection until he gets the one that he wants to work with. > > > > The only way that I could achieve the user being able to tap on any area > > in > > the polygon and get the right image was to make a color map and overlay > > the > > original image over the top of it. > > > > In other words the user sees the states image but when the user taps the > > ppc > > gets the location of where the user taps and the pixel color from the > > underlying colormap of RGB colors. The RGB color is turned into an argb > > color > > value that has references in a database table to tell the program what the > > user clicked. > > > > Kinda hard to explain but I think you might get the idea. I am very open > > to > > an easier way to achieve this if anyone has one. > > > > Thanks everyone for helping me. I really appreciate it. > > > > ------------------------------------------ > > Noble D. Bell > > AgForest Partners, Inc. > > > > > > > > "<ctacke/>" wrote: > > > >> > Thats interesting. If that is the case then how would one ever take the > >> > argb > >> > value of a pixel and look it up in a database table against a list of > >> > values > >> > if the pixel argb value could be different on different hand helds? > >> > >> I've got no idea why you'd want to look it up in a database, but you can > >> always strip the LSBs and do a lowest-common-denominator comparison. > >> > >> > > >> > What is the norm on ppc's for color depth nowadays? 16-bit? 32-bit? > >> > > >> > >> There is no "norm". 12 and 16 bit are the most common. It's unusual to > >> see > >> more depth, as most displays of the size you're looking at don't support > >> any > >> higher depth, so it's just a wast of memory and bus bandwidth. > >> > >> -Chris > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |