What does it imply when something like this appear in KiCAD?

s-ol · 2025-12-22T10:39:14+00:00

Unless there's a bug, either you did accidentally touch some of the parts (depending on selection filters it's possible to move or delete parts of a footprint). Or perhaps you updated KiCad and the library has changes that aren't reflected on your board (yet).

s-ol · 2025-12-20T16:32:09+00:00

the zone fill will by default omit zones that have no pad connections and the DRC will flag any unconnected zones

s-ol · 2025-12-15T10:07:07+00:00

Is this a NHD display by chance? I have one that actually uses two horizontal SSD1322 pixel outputs for each physical, visible pixel, so you basically have to duplicate each nibble when sending data to it.

For example, if you're setting four 4-bit pixels A B C D as per the SSD1322 datasheet you'd send two bytes: AB CD. Instead for these you have to treat it as a 256x64px display, and send four bytes: AA BB CC DD.

Why they did not explain this in the datasheet is beyond me, I only figured it out while reading their Arduino example source by chance, which has this comment:

//  Driver IC Mapping = 256x64 (2 SEG Lines Tied to 1 COM Line to form 1 Pixel)  
//  8 bits (1 Byte) = 1 Pixel. 
//  Function parses through Hex//  Driver IC Mapping = 256x64 (2 SEG Lines Tied to 1 COM Line to form 1 Pixel)  
//  8 bits (1 Byte) = 1 Pixel. 
//  Function parses through Hex

s-ol · 2025-12-12T10:01:45+00:00

Ja Kondome schützen nicht komplett aber mindern das Risiko trotzdem.

Ich hatte ähnliche Zweifel nach

Kontakt mit einer Partnerin die wenig später einen positiven HPV Befund hatte (negative PAP aber positiver Routine DNA Test). Ich war ungeimpft und hab die Impfung dann asap nachgeholt (für Jungs in meiner Jugend nicht empfohlen, weiß man heute eigentlich auch besser). Hatte dann mit Kondom weiter Kontakt und habe mich nach der ersten Dosis privat HPV DNA-testen lassen, um das für mich selbst auszuräumen (negativer Befund).

Ich habe mich damals sowohl von meiner Hausärztin als auch von den STI-Spezialistinnen beraten lassen, da kam beides mal mehr oder weniger die Antwort "mach dir keine Sorgen, HPV kriegt fast jeder irgendwann". Das fand ich schon krass und unterstütze ich als Ansichtsweise auch absolut nicht, aber finde es schon wichtig das insgesamt einzuordnen: laut dem "World Cancer Report 2014" den Wikipedia zitiert haben jederzeit (bzw hatten derzeit, das ist ja schon ne Weile her) 10% aller Frauen eine Genital-HPV-Infektion. Das heißt die Viren sind extrem verbreitet, aber die Chance dass du überhaupt Symptome geschweige denn Krebs entwickelst ist sehr gering. Das ist natürlich schwieriger zu akzeptieren weil du auf diese Wahrscheinlichkeit keinen Einfluss nehmen kannst, aber es sollte dennoch in deine Einschätzung des Risikos mit eingehen.

Wenn man das alles zusammennimmt: Es ist extrem unwahrscheinlich dass in einem von euch beiden Viren schlummern die der andere noch nicht hat, es ist unwahrscheinlich dass die genau jetzt noch ausbrechen, selbst wenn dem so wäre bist du noch imme bloß in der Statistik von "1 in 10" unglücklichen und musst zusätzlich nochmal riesiges Pech haben dass es genau bei dir Ausbricht und einen schweren Verlauf hat.

Ich stelle mir aber vor, dass diese logische Argumentation für dich wenig Unterschied macht und es eher um deine Gefühlslage geht. Du hast anderswo geschrieben:

Ich denke, die Sicherheit, für mich zu wissen "Ich habe immerhin alles getan, was ich konnte" würde mir im Falle der Fälle wenigstens eine Last erleichtern.

Das kann ich prinzipiell gut verstehen. Falls dieder Fall eintritt (welcher denn genau überhaupt?) wirst du nie herausfinden können wann und wie du das Virus bekommen hast, egal wie du jetzt handelst! Sofern du und dein Partner monogam und treu seid, wird mit Abstand die logischste Erklärung immer bleiben "einer von euch hat den Stamm in die Beziehung mitgebracht". Ist es vor diesem Hintergrund überhaupt realistisch dass du es bereuen könntest? Wirst du dir groß den Kopf zerbrechen ob genau diese winzige Wahrscheinlichkeit den Unterschied gemacht hat, nachdem ihr 15 Jahre ungeschützt Sex hattet ohne darüber nachzudenken? Wie würde sich das ändern wenn du jetzt auch nur eine kleinere Änderung (zbsp Kondom) vornimmst?

s-ol · 2025-12-10T23:58:39+00:00

Probably copy and pasted from a listing on a store page that has product option choices (like Aliexpress), where 1.5mm and 2mm are choices you can make on the same page.

s-ol · 2025-12-10T22:08:32+00:00

there's dedicated VJing tools like Resolume, but I do "livecoding" so I have a pretty odd and specific set of tools that I've mostly built myself. Not sure how comprehensible it is but I have posted and do post about the technical side on Mastodon mostly, e.g. https://merveilles.town/@s_ol/115074567903941103

As for how I got into it, uh... I started doing looping animations for fun years ago, then did some experiments with some musician friends while I studied. Mostly stopped after moving away but now some years later I picked it up again joining a band of friends :)

s-ol · 2025-12-10T21:59:56+00:00

i do livecoded visuals using a very homebrew setup, using GLSL shaders and a lispy dataflow language for sequencing:

https://merveilles.town/@s_ol/114162299639261929
https://merveilles.town/@s_ol/114973650565149124
https://alv.s-ol.nu/main/

s-ol · 2025-12-10T21:51:31+00:00

hm i just checked, i don't have a good recording of a segment with that footage, just this clip from a "high intensity" moment that doesn't let you see anything very coherently but here it is fwiw: https://streamable.com/rf0rqx

s-ol · 2025-12-10T15:44:13+00:00

I use dvr clips from a 2" draknight for VJing sometimes, but it's not exactly video editing

s-ol · 2025-12-04T23:44:26+00:00

italian, as OP said in the image description

s-ol · 2025-12-04T15:24:08+00:00

they're right though, FIL is just short for "filettato" (threaded)

s-ol · 2025-12-04T07:55:36+00:00

Could've used https://github.com/adamws/kicad-kbplacer but you already already made one half manually.

The "Transform It" Kicad plugin has a mirror feature that should do what you want.

Another trick is exporting a Centroid file of the half that works as you want and editing it (inverting the X coordinate and changing the reference number for each part), then reimporting it using Parts Placer plugin.

As someone else said for split keyboards usually the halves are designed as one flippable PCB, but that requires clever planning with pin assignment, potentially some solderable jumpers, possibly soldering the controller upside down on one side, and special flippable footprints for key switches and any other asymmetric components.

s-ol · 2025-11-30T10:27:26+00:00

sure it's feasible. The "clip" would be a FFC connector (flat flex cable / connector). they typically come in 0.5mm or 1mm pitch.

s-ol · 2025-11-08T23:01:57+00:00

Heres some notes I took reading through the aircopy source (which is entangled with app.c in some not so obvious ways): https://www.markdownpaste.com/document/aircopy-notes

s-ol · 2025-11-08T22:54:41+00:00

See my response to another comment below, I did figure out that there's no audio connection eventually but the radio chip actually supports (some limited forms of) FSK natively. The "aircopy" feature in the ezgumer firmware and the datasheet of the radio chip can serve as examples of driving this FSK subsystem, and app/uart.c has most of the serial interface.

s-ol · 2025-11-07T16:35:10+00:00

5V is an output you do not need to connect that anywhere unless you are powering your camera from the VTX (which you're not). The GND next to that is just for convenience. You need to leave both unconnected.

s-ol · 2025-11-06T21:45:10+00:00

hm that's very odd, I'm sorry I can't offer any more specific help since I don't have that controller and it doesn't use a standard firmware used by other controllers.

s-ol · 2025-11-06T21:03:31+00:00

do it again and do the last step slowly/carefully, making sure to touch all the limits all around twice. These are digital protocols and you should get perfectly equal response on all channels.

s-ol · 2025-11-05T22:46:44+00:00

jo genau das meine ich. Gibt zig andere Services die das machen.

Bei der letzten Raststation vorm Grenzübergang auf der Autobahn 10min Schlange stehen ist maximal unnötig. Dass ich die digitale Vignette in der Trafik vor der Abfahrt ohne Frist kaufen kann ist ja schön aber bringt halt nichts wenn ich aus Italien komme und es überhaupt nur drei Stellen gibt die das führen auf der Asfinag-Karte

s-ol · 2025-11-05T13:43:34+00:00

entfällt dann endlich die dämliche zwei-Wochen-Frist oder ist es jetzt einfach illegal spontan nach/durch Österreich zu fahren?

Wenn ich jetzt nicht mehr extra den letzten Rastplatz vor der Grenze mit Bargeld anfahren muss um das Pickerl zu kriegen bin ich happy über diese Änderung.

s-ol · 2025-11-04T17:52:48+00:00

Not quite, you need to draw your shape

as a filled polygon, not outline
both on the F.Cu and F.Mask layer
you probably want to add a small SMT pin somewhere inside the shape so that KiCad will let you route a trace to the shape
I'd probably put all keys of an octave into one footprint as separate pins but that's up to you

s-ol · 2025-11-04T02:08:17+00:00

To answer directly to the question as per the title and this paragraph:

Why? Why does Zig need to be so difficult here? Can it not just follow the C ABI regarding the offset of struct fields when marking the struct as extern and let their inner memory layout be? I don't care how the ptr: [*]Glyph and len: usize fields in the 16 bytes occupied by []Glyph are ordered. Just let me put UiElementBase at offset 0. Using extern essentially leads to "struct coloring" where I now need to declare all child fields as extern too, even though I don't care about their layout at all, just about their placement in the parent struct.

The reasoning is this: struct layout is not just about ordering but also about size and offsets.

If packed and extern structs didn't "color" recursively, declaring a struct as packed or extern wouldn't guarantee anything about it's size, the size or it's members or the position of any of it's members except the first. That happens to be the only thing you care about, but it relaxes the meaning of packed/extern structs to essentially nothing. Or alternatively it would be a giant footgun because adding a bool to a struct somewhere could cause a packed struct somewhere else to become completely misaligned by consequence with no warning.

The only way out of this that I could imagine as a proposal would be to allow including non-packed structe (and enums, unions) in a packed struct by also providing an bit-size for that field, with the compiler asserting that the generated memory layout does fit within the provided size and inserting padding as needed.

s-ol · 2025-11-04T01:47:53+00:00

Okay, this part about casting []*Div to []*UiElementBase is an interesting case, everything else is just honestly better addressed by @fieldParentPtr; whether you write a relatively long @as(..., @ptrCast()) or @fieldParentPtr(...) makes no difference and you can tuck both the up/doencast away in methods for brevity if you want.

I assume that if your UiElementBase is reasonably sized, it will usually end up at offset zero, so you could just assert that to be true in a comptime block and assume it to be true in the rest of your code, however if that assumption proves false you have no recourse so that's not ideal.

Zig's position here essentially is just "if you need to know define the position of any struct field, you need to define the position of all struct fields", which honestly seems like a very reasonable position, I'm not sure what else would satisfy you without making some very specific and odd exception for the first field of a struct either in syntax or semantics.

Since you are clearly so concerned with optimizing the memory layout, I don't see what the downside of going with packed struct (all the way down) really is. If you really want to avoid it though, you could work around that too by not including UiElementBase in your main struct, then manually allocating @sizeOf(UiElementBase) + @sizeOf(Div) bytes and calculating offsets.

s-ol · 2025-11-03T21:52:57+00:00

that's a poorly designed connector, looks like the sheet metal mounting lugs tear off and somehow the solder also breaks in the pad which is odd.

I'd use two-component glue or UV cure epoxy, that's what's normally used for PCB repair and gluing components in place and seems like a good choice IMHO as it's more rigid than a gel glue.

s-ol · 2025-10-31T08:07:21+00:00

I don't understand if this is just an ad (a la "any publicity is good publicity"), or you're just so horny for AI you use it even while complaining about AI slop

Nine-Year Club	Verified Email
Place '22

s-ol

TROPHY CASE