Right. Let's say you have four 256x256 textures... you can pack them into a single 512x512 texture, which is often convenient, especially when the textures tend to occur together. Now, when a graphics card does texture mapping, it sort of assumes that the portion of the texture it's painting on one triangle spills over onto the other faces of the polyhedron... that is, that it's wrapping the texture, in some way, around the polyhedron. One of the consequences of this assumption is what we're seeing here. In multisampling FSAA, you look at a set of points, not just the pixel center, to figure out what color to display in the pixel. In the center of a face, this works fine; the points are all in the desired pixel, all on the same face, and you get the correct effect. Towards the edge of a face, though, some of the points chosen may be past the edge of the texture boundry. If the texture wraps (that is, continues), it will be more or less the same color; we may see a tad of color from something that, strictly speaking, should be on the next face, but this is a non-issue. However, what if we're at the end of the texture? Normally this is detected and special-cased; either they wrap around to the far end of the texture or, more likely, they just throw out the given point. However, here, we're at the end of what the programmer thinks of as a texture, but not what the hardware thinks of as a texture... so it averages in a little bit of totally wrong coloring in the pixels at the edge of a polygon, under certain conditions. Solutions? Hardware side: Have the card only pick pixels within the polygon, which should therefore also be within the texture; the above describes only if you have some mismatch, like getting points from the far side of pixels that are part of the polygon on screen, but only partially inside the polygon in fact. Developer side: Don't pack textures.
What does being a US citizen have to do with anything? Applying for work in India, you are not covered by US minimum wage laws, which apply to areas under US jurisdiction... for now, the US. Laws differ all of the world, regardless of your nationality. For example, some places may consider murder by an american football player an offense, even though the guy's a celebrity. The football player, even though he's an american citizen, is likely to run into difficulties if he commits murder outside his home country.
On the other hand, anyone who thinks that parents should know everything, free of charge (where the charge, currently, is having to interact with the child) has never been a kid.
I've never clicked on one of these ads. Neither has my mother - she's a social worker. Neither has my grandmother - who was a housewife for most of her 85 years. Neither has my father - a lawyer, who learned wordperfect and not much else. Neither has anyone else I can think of. Oh wait, they all use macs./offtopic
But until they actually download (in your example) Photoshop's intellectual property, they don't know for sure that it/is/ Photoshop's property, and not the site owner's. That is, they're agreeing to a click-through license in bad faith, with full intention of breaking it. The fact that the other side happens to break it also does not change the fact that the Fed decided to ignore it, does it?
I should point out that I actually got this idea, at least vaguely, from somewhere, although I don't recall where (possibly the wonderful mindprod.com website). But it seems to me that there is a natural bridge between the two concepts, gestures and pie menus, in that they allow access to the same functions with the same motions, just with different amounts of visual cues.
The best way, in my opinion, to teach gestures is by pie menus. They're basically the same thing. Let's say that we have gestures that distinguish between 8 directions (N, NE, E, SE...), and are brought up by clicking the right button and gesturing. In "teach mode", clicking the right button should bring up a pie menu, with the eight slices marked in some manner. (Note that this requires gestures to have some pattern to their meaning.) So, if forward is N, E and back is N, W.... both of those gestures could be done normally, but in teach mode the N label on the menu would say "Navigation", for instance... going in the direction would bring up another pie menu, with E as forward, W as back, and maybe S as home. So by selecting things from these familiar hierarchical menus, you're learning into muscle memory the movements that work in gesture mode, when you remove the visual cues. Make sense?
I'm as big a G4 fan as the next... but it really seems that, for integer work, the Centrino setup (processor plus chipset determines speed, not processor alone) tops a G4 setup, both clock-for-clock and watt-for-watt. The G5 should fix both of those; the G3 fixes only the watt-for-watt.
Or you can get your paragliding (P2) certificate, plus your own paraglider, plus the best instruction in the world (www.paraglide.com -- I don't work for 'em, I just love 'em) for the same $5000. No doubt that each appeals to different people... but I wanted to not only fly, but feel the wind around me, feel myself in direct control... and paragliding provides that for me.
Do one square per pixel of source image, colored squares (no texture)... and use the raw data (RGB), with the pixel grid in place. That is, don't use the combined RGB values; each pixel should be some saturation of one of red, green, or blue. Antialiasing and filtering, then, should give you the optimal (combined RGB) image, either before or after distorting.
On the same note, I always thought it would be nice if, if apple is really going to stick with this one-button strategy, they made the touchpad touch-surface the whole size of the touchpad. That is, eliminate the button entirely, and just support tapping on a larger surface. And since apple uses touchpads with the same aspect ration as their monitors, it would make the touchpad significantly wider as well... bigger is better, when it comes to control surfaces, whether on airplanes or laptops.
How hard would it be to do this as a home-made mod? Even if a company were to come out with a two-button trackpad add-on (which I would love, even though I don't have a personal need for it; choice is good), it ain't going to be for anything older than a albook / ibook (I'm surprised this keyboard is for the nearly-dead tibook). Looking at my ibook, the clicky thing (button) is right in the center of the trackpad button, so the right-hand third of the button could be removed without problems. This leaves a left-click button larger than the potential right button, but as left-click is more common anyway, this could be argued away as a good thing. Now, what can we put in the space we have? I haven't looked inside an ibook for a while, but imagine we're quite space-limited. Even so, it shouldn't be hard to wire in something from a membrane keypad or some such, or even or a more typical switch in the available space. Now, how to connect it? I suspect this is where we get bit, although on an albook without bluetooth, it's manageable. The bluetooth modules in the albooks hook up to usb headers. All you need is the board out of a usb mini-mouse, wire it up to the usb sensor, and rewire the right-button switch to use the switch you added. To the OS, the left and right button signals will appear to come from different mice, but that should be acceptable. The iBook, at least, has enough empty space for an additional circuit board that size (wrap it in electrical tape and just stick it in somewhere)... haven't been inside an albook yet.
Anyone have any suggestions for improvement to this technique?
What part of the class library? Unless you think C is some instance of a standard class from the class library... but I can't think of a single class with a length member variable. I was assuming that C was an array which, although it extends Object in java, is not a class from the class library.
Now, assuming this also works on Collections objects, it will, indeed, be a hack, but no more so than serialization or cloning. We've done worse things to java for less reward.
I don't know why I was modded troll, and I don't know why you think I'm lying... I really was sharing my honest opinion and experience. What questions did you find difficult to understand? I thought it was quite straightforward and well written, at least for ETS. Certainly better written than, say, the verbal section of the standard GRE.
Slashdot Mirror
Nvidia is diety!
There are so many jokes I can make about this I can't even choose one...
Probably (almost certainly) not. See my attempted explanation.
Right. Let's say you have four 256x256 textures... you can pack them into a single 512x512 texture, which is often convenient, especially when the textures tend to occur together. Now, when a graphics card does texture mapping, it sort of assumes that the portion of the texture it's painting on one triangle spills over onto the other faces of the polyhedron... that is, that it's wrapping the texture, in some way, around the polyhedron. One of the consequences of this assumption is what we're seeing here. In multisampling FSAA, you look at a set of points, not just the pixel center, to figure out what color to display in the pixel. In the center of a face, this works fine; the points are all in the desired pixel, all on the same face, and you get the correct effect. Towards the edge of a face, though, some of the points chosen may be past the edge of the texture boundry. If the texture wraps (that is, continues), it will be more or less the same color; we may see a tad of color from something that, strictly speaking, should be on the next face, but this is a non-issue. However, what if we're at the end of the texture? Normally this is detected and special-cased; either they wrap around to the far end of the texture or, more likely, they just throw out the given point. However, here, we're at the end of what the programmer thinks of as a texture, but not what the hardware thinks of as a texture... so it averages in a little bit of totally wrong coloring in the pixels at the edge of a polygon, under certain conditions. Solutions? Hardware side: Have the card only pick pixels within the polygon, which should therefore also be within the texture; the above describes only if you have some mismatch, like getting points from the far side of pixels that are part of the polygon on screen, but only partially inside the polygon in fact. Developer side: Don't pack textures.
Is it "free"?
It "is".
Gotta fess up... about 2600 of those were me. I was bored.
What does being a US citizen have to do with anything? Applying for work in India, you are not covered by US minimum wage laws, which apply to areas under US jurisdiction... for now, the US. Laws differ all of the world, regardless of your nationality. For example, some places may consider murder by an american football player an offense, even though the guy's a celebrity. The football player, even though he's an american citizen, is likely to run into difficulties if he commits murder outside his home country.
I need an excuse to upgrade to carbon...
On the other hand, anyone who thinks that parents should know everything, free of charge (where the charge, currently, is having to interact with the child) has never been a kid.
I've never clicked on one of these ads. Neither has my mother - she's a social worker. Neither has my grandmother - who was a housewife for most of her 85 years. Neither has my father - a lawyer, who learned wordperfect and not much else. Neither has anyone else I can think of. Oh wait, they all use macs. /offtopic
How does Mario Bros. not tell a story? /me runs off to rescue the princess.
Um... C is C(\+)*.
But until they actually download (in your example) Photoshop's intellectual property, they don't know for sure that it /is/ Photoshop's property, and not the site owner's. That is, they're agreeing to a click-through license in bad faith, with full intention of breaking it. The fact that the other side happens to break it also does not change the fact that the Fed decided to ignore it, does it?
I should point out that I actually got this idea, at least vaguely, from somewhere, although I don't recall where (possibly the wonderful mindprod.com website). But it seems to me that there is a natural bridge between the two concepts, gestures and pie menus, in that they allow access to the same functions with the same motions, just with different amounts of visual cues.
The best way, in my opinion, to teach gestures is by pie menus. They're basically the same thing. Let's say that we have gestures that distinguish between 8 directions (N, NE, E, SE...), and are brought up by clicking the right button and gesturing. In "teach mode", clicking the right button should bring up a pie menu, with the eight slices marked in some manner. (Note that this requires gestures to have some pattern to their meaning.) So, if forward is N, E and back is N, W.... both of those gestures could be done normally, but in teach mode the N label on the menu would say "Navigation", for instance... going in the direction would bring up another pie menu, with E as forward, W as back, and maybe S as home. So by selecting things from these familiar hierarchical menus, you're learning into muscle memory the movements that work in gesture mode, when you remove the visual cues. Make sense?
Galium Arsenide? Perhaps you refer to Gallium Arsenide?
Fritz is multithreaded. FritzMark, the benchmarking program that uses instruction sequences similar to those in Fritz, is not.
I'm as big a G4 fan as the next... but it really seems that, for integer work, the Centrino setup (processor plus chipset determines speed, not processor alone) tops a G4 setup, both clock-for-clock and watt-for-watt. The G5 should fix both of those; the G3 fixes only the watt-for-watt.
Or you can get your paragliding (P2) certificate, plus your own paraglider, plus the best instruction in the world (www.paraglide.com -- I don't work for 'em, I just love 'em) for the same $5000. No doubt that each appeals to different people... but I wanted to not only fly, but feel the wind around me, feel myself in direct control... and paragliding provides that for me.
Paragliding. www.paraglide.com. Enjoy.
Do one square per pixel of source image, colored squares (no texture)... and use the raw data (RGB), with the pixel grid in place. That is, don't use the combined RGB values; each pixel should be some saturation of one of red, green, or blue. Antialiasing and filtering, then, should give you the optimal (combined RGB) image, either before or after distorting.
I'm going to be going down to Melbourne from the states in a month or two... if you need help with smuggling, give a yell.
adam at addaon dot com
On the same note, I always thought it would be nice if, if apple is really going to stick with this one-button strategy, they made the touchpad touch-surface the whole size of the touchpad. That is, eliminate the button entirely, and just support tapping on a larger surface. And since apple uses touchpads with the same aspect ration as their monitors, it would make the touchpad significantly wider as well... bigger is better, when it comes to control surfaces, whether on airplanes or laptops.
How hard would it be to do this as a home-made mod? Even if a company were to come out with a two-button trackpad add-on (which I would love, even though I don't have a personal need for it; choice is good), it ain't going to be for anything older than a albook / ibook (I'm surprised this keyboard is for the nearly-dead tibook). Looking at my ibook, the clicky thing (button) is right in the center of the trackpad button, so the right-hand third of the button could be removed without problems. This leaves a left-click button larger than the potential right button, but as left-click is more common anyway, this could be argued away as a good thing. Now, what can we put in the space we have? I haven't looked inside an ibook for a while, but imagine we're quite space-limited. Even so, it shouldn't be hard to wire in something from a membrane keypad or some such, or even or a more typical switch in the available space. Now, how to connect it? I suspect this is where we get bit, although on an albook without bluetooth, it's manageable. The bluetooth modules in the albooks hook up to usb headers. All you need is the board out of a usb mini-mouse, wire it up to the usb sensor, and rewire the right-button switch to use the switch you added. To the OS, the left and right button signals will appear to come from different mice, but that should be acceptable. The iBook, at least, has enough empty space for an additional circuit board that size (wrap it in electrical tape and just stick it in somewhere)... haven't been inside an albook yet.
Anyone have any suggestions for improvement to this technique?
What part of the class library? Unless you think C is some instance of a standard class from the class library... but I can't think of a single class with a length member variable. I was assuming that C was an array which, although it extends Object in java, is not a class from the class library.
Now, assuming this also works on Collections objects, it will, indeed, be a hack, but no more so than serialization or cloning. We've done worse things to java for less reward.
I don't know why I was modded troll, and I don't know why you think I'm lying... I really was sharing my honest opinion and experience. What questions did you find difficult to understand? I thought it was quite straightforward and well written, at least for ETS. Certainly better written than, say, the verbal section of the standard GRE.