Which of these two loops is "better"?

Code:

  while (!var)
  {
    //code
    if (something)
    {
      var = 1;
    }
  }

or

Code:

 
  while (1)
  {
    //code
    if (something)
    {
      break;
    }
  }

They both do the same thing obviously, and I can use either one for part of my code so I was just wondering if one is prefered over the other. I would guess the first one is better since break seems to have the same reputation as goto. I've had a lot a similar situations while coding in the past; Is there a place where all these coding conventions are written out?

Huh?

It was quite a while ago so I don't remember the details, but it was an IDE version between 0018 and 0022 I think.

I have a similar synaptics trackpad with the same pinout. It worked flawlessly with the ps2 library when I last tried it.

I once heard somewhere that a specific natural occuring shape of crystal would oscillate at exactly 32.768 khz. Don't know if this holds any truth though

I probably should have mentioned that I'll be winding the secondary myself, so there will be no confusion as to which side of the winding is where. I just wanted to check if this was even possible, as it's much easier to wind several thin coils than it is to wind one very thick coil.

Probably a simple question, but I can't wrap my head around it. Lets say I have a transformer with 2 identical secondary windings wound in the same direction. Can I connect them in parallel to double the current they can handle? Is this essentially the same as using one winding of double the thickness? It just doesn't seem right because the wires are insulated from each other except for at the ends, but google suggests that it's possible.

I guess regular old thermal grease would work. Thermal exopy if you want a permenent contact. But either way, thet will be package temp, not die temp. Maybe with a bit of math and the thermal conductivity figures in the datasheet it would be possiblr to get an accurate measurement

Yeah, it should work. Take a look at section 20.3 for proper connections

Take a look at the datasheet, it talks about different methods for powering the thing if I remember correctly. Various voltages, powered from USB, powered from external source, etc.

Has anyone tried making their own solder mask for homemade PCB's? I'll be using some 0.5mm TQFP packages on an upcoming project and it would be nice if I could get some sort of solder mask between the pins to reduce solder bridges when drag soldering. So far my best idea is to spray the whole board with high temp spray paint and scrape away the paint on the pads with a knife. Alternatively I've seen high temp. felt tip markers which might be less messy. Does this sound feasible? Does real solder mask have some special property which makes it repel solder? And, no, I'm not interested in making a stencil and using UV curable paint.

Typically arduino code doesn't have functions for low level stuff like this. You'll have to use good old avr register writes.

Yeah it surprised me too when my first one got shorted. I just redid the less-than-adequate solder job and the problem seems to have gone away; must have been flux residue. However on my first touchscreen the solder job was perfect, yet the short didn't go away over time. Weird.

What is typically the maximum voltage I should apply between y+/y- or x+/x- on a resistive touchscreen? the resistance is about 300 and 500 ohms for x and y, respectively. I'm asking because I seem to have broken my first touchscreen by using 3v. The resistance between x- and y- became 100 ohms when the touchscreen wasn't pressed (it should have been infinite ohms). I just got a new touchscreen and was also using 3v when the same thing happened. If I disconnect the power and measure resistance it rises up to ~100k over the course of 30 seconds, so it might be something else. Is 3v way to much for the touchscreen? I'd like to drive it directly from an MCU output.

I think it would be easier to just buy some transistors which can handle the voltage and solder them in instead