Prev: URGENT
Next: DataRow InsertAt Database
From: Random on 6 Nov 2009 20:45 On Nov 6, 4:29 pm, Loren Pechtel <lorenpech...(a)hotmail.invalid.com> wrote: > >Which source file? There are two for any form created in visual > >studio. One (the .Designer.cs) should be pretty much nothing but > >properties you set in the form designer. > > Yeah--but without it how is it going to work? It won't, of course. Since the .designer.cs file is just normal everyday code, you can combine the two files (and trim out bits unrelated to your problem description) and post the results. Or, even better yet, there's nothing stopping you from creating a form from the ground up like's been shown in a couple of examples now.
From: vanderghast on 7 Nov 2009 07:52
indeed, if there is even one pixel of difference in size between the two bitmaps sizes, a "BitBlt" (tile zoom to fit the space, GDI+ may have another name for that function) may screw the whole one-to-one representation and that is where a blur or other inconsistencies could easily show up. A textured brush would take your available bit map and would not try to resize it in any way, but rather repeat it (tile it) or crop it as required, *if* the problem is one linked to the area size. If it is a problem linked to a poor driver or of monitor resolution, though, it *may* not help, indeed. Vanderghast, Access MVP "Loren Pechtel" <lorenpechtel(a)hotmail.invalid.com> wrote in message news:%23kxo7AyXKHA.1236(a)TK2MSFTNGP05.phx.gbl... > On Fri, 6 Nov 2009 09:36:27 -0500, "vanderghast" <vanderghast(a)com> > wrote: > >>As you said, it is between the bitmap, which is ok, and the screen. That >>betweeness includes the video card and the monitor driver. If you captured >>the image, you read what is in the video card (I assume the monitor >>memory >>is write only in most cases), and it seems to prove that the image is ok >>there too. So even if you are in native resolution, maybe you use generic >>driver for the monitor, rather than the manufacturer one? Furthermore, as >>proven by the image I posted (which was captured by an external camera), >>your code ***works*** fine. Can you try on another PC? > > But when I save the bitmap and load it with another program *ON THE > SAME MONITOR* it works. > > Thus the system is messing with it (probably scaling it on the x-axis) > somewhere between the bitmap and the screen. > > I have a panel on the form, in the panel a picturebox and the image is > put in the picturebox. This is because there is a minimum size the > image must be in order to convey needed information, if I have more > space available than that I try to fill it with optional information > rather than let it go to waste. > >>A texture can repeats itself (wrap mode) to fill variable size area, >>rather >>than being limited to enlarge its original 'pixels' to fit the area, and >>will even fill convex area with matching the pattern (example, painting a >>T, the texture in the steam is aligned with the texture in the flanges, >>automatically... if you use the same brush to paint). See "Pro .Net 2.0 >>Graphics Programming", by Eric White, at Apress, pp49+ > > I'll have a look, although all the texture work is done so I probably > won't touch it. |