• 3 Posts
  • 497 Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle


  • You totally should power your Raspberry Pi through GPIO pins, once you grow up from blinking LEDs on your table to assembling some automation equipment that you expect to work at other people’s premises.

    MicroUSB connection is the one biggest point of failure in any kind of Raspberry Pi automation project. Type-C socket is better, but it still depends on your cable to have appropriate quality, and if your project involves vibration, the cable may and will slip out.

    If you don’t want your Pi to randomly stop working in two years, choose a good-quality power supply and solder it to 40-pin DuPont socket header. Do not use individual socket wires, they need very little effort to get loose. If you’re paranoid, you can solder it directly to Raspberry Pi pins, but obviously you won’t be using that particular Pi for any other project, also you should use heat shrink tubes.

    but the only thing that’s broken is the fuse which can easily be replaced.

    Lolno. You’re not replacing any SMD fuses without a heat gun and a workbench with a magnifying glass. Raspberry Pi 4 and 5 do not have fuses at all, overvoltage directly fries your PMIC and the replacement is impossible to find.

    Source: I own a fried RPi 4, and several RPi Zero, one of which failed to boot because MicroUSB cable wiggled in a socket.














  • TreeView is designed as an afterthought. Some manager at MICROS~1 was like ‘ah yes we need an expanding nested list widget by tomorrow’ and they mutilated text edit box to draw text lines that expand when you click them. It does not have keyboad focus. It can only be operated with a mouse. It does not have shadow or raised widget borders. It has black text on white background, while every other widget has Windows Gray background.

    The proper UI would be a separate button for each label, like multiple hierarchical combo boxes.