• 11 Posts
  • 48 Comments
Joined 9 months ago
cake
Cake day: September 26th, 2023

help-circle




  • This ties into the comment I was going to make separately. For context, my dad recently passed. First father’s day without him. My mom asked to watch a movie that meant something to the both of them because they saw it together in a drive in on release and it was very memorable because the technology and techniques used were fascinating at the time. She complained that it wasn’t on Disney+ or anywhere.

    You may have guessed it, but she requested Song of the South. One serious moral quandary later, I got it ready for her to watch.

    Tomorrow is gonna be rough, but at least my sailing might bring some good memories for her.





  • jawa21@lemmy.sdf.orgtoMemes@lemmy.mlts moment
    link
    fedilink
    arrow-up
    44
    arrow-down
    1
    ·
    1 month ago

    The real question is: How in the world did Ventrillo continue to exist after TeamSpeak came along?

    Vent was an object lesson in hostile UX. It sounded like shit, changing any kind of setting (even basic things like individual volumes) was a a gymnastics routine, and mics constantly clipped despite settings.















  • I worked with Fanuc control machines for 20 years up until 2023. Sounds like you were needlessly in macro hell. Just declaring an offset will use either an H (typically height) or D (typically a radius offset in Fanuc controls, but sometimes they are setup for diameter).

    It would go something like this:

    G40G49G80G90 (CLEARS OUT POTENTIALLY PREVIOUS GCODES);
    
    
    T1M06 (EXECUTES A TOOL CHANGE, LEAVE OUT M06 IF JUST DECLARING THE TOOL);
    
    
    G43H01 (DECLARES H01 AS THE HEIGHT OFFSET);
    
    G00ZO.O1 (MOVES THE TOOL 0.01 ABAOVE WORK);
    
    G41D01X1.0 (DECLARES LEFT HAND TOOL OFFSET AS D01);
    

    You don’t need true macro variables for 9/10 applications, or general operation. I feel like you got placed on some overenginered solution.