@mcdanlj@social.makerforums.info
@mcdanlj@social.makerforums.info avatar

mcdanlj

@mcdanlj@social.makerforums.info

1st Fedora Project Lead. Co-author Linux Application Development. Sr. Director Engineering Pendo. Ex-{Linux Journal, Red Hat, rPath, SAS}. Christian. Father. Maker (including machining, 3D printing, and electronics). Books. Classical music. Aviation (inactive PP-Inst-SEL). https://musings.danlj.org/

#searchable searchable (please index my posts for search purposes)

This profile is from a federated server and may be incomplete. Browse more on the original instance.

mcdanlj, to random
@mcdanlj@social.makerforums.info avatar

How long has #FreeCAD had the TechDraw dimension repair tool? Have I been replacing instead of repairing dimensions for a long time needlessly? Will the TNP mitigations make it into TechDraw and make dimension repair infrequently needed?

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@yorik Thanks! A flurry of TechDraw_DimensionRepair bugs have just been filed to help get to 1.0. ☺

mcdanlj, to random
@mcdanlj@social.makerforums.info avatar

I just spent an hour putting together a detailed bug report on a 100% repeatable SIGSEGV in a local build of #FreeCAD from a few hours ago, and before hitting submit, I pulled the latest code and rebuilt it.

It was already fixed.

This is hard to complain about. 😎

FreeCAD, to random
@FreeCAD@fosstodon.org avatar

WIP Wednesday 15 May 2024
This week in FreeCAD development:

Toponaming: bgsbww spent some time adding missing bits of toponaming code to core, Part Design, and Sketcher.

Measure tools got some really useful updates. hlorus made some improvements to the new unified measurement facility and added measurement values to labels in the project tree. Meanwhile wwmayer rewrote parts of the new Quick Measure
https://blog.freecad.org/2024/05/15/wip-wednesday-15-may-2024/

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@FreeCAD The new Quick Measure tool is great. And the smart dimension tool in TechDraw will be such a time-saver! I hope it gets a hotkey soon, as in the Sketcher workbench, to make it more accessible.

nervous_jessica, to random
@nervous_jessica@mastodon.social avatar

I just found a tick in the laser room :(

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@nervous_jessica At least you have appropriate tools for disposal at reach there. 😬

mcdanlj, to random
@mcdanlj@social.makerforums.info avatar

I've finally built #FreeCAD for myself, with the TNP mitigation enabled. Now every time I see something cool in the @FreeCAD WIP Wednesday posts I can play with it without waiting for a new weekly build. ☺

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@trevorflowers Details at https://github.com/FreeCAD/FreeCAD/issues/13983 but:

toolbox create --name debian --image debian:latest<br></br>toolbox enter debian<br></br>apt-get install --no-install-recommends --yes build-essential cmake doxygen <br></br>    git libboost-date-time-dev libboost-dev libboost-filesystem-dev <br></br>    libboost-graph-dev libboost-iostreams-dev libboost-program-options-dev <br></br>    libboost-python-dev libboost-regex-dev libboost-serialization-dev <br></br>    libboost-thread-dev libcoin-dev libeigen3-dev libgtkglext1-dev libgts-dev <br></br>    libkdtree++-dev libkml-dev libmedc-dev libocct-data-exchange-dev <br></br>    libocct-draw-dev libocct-foundation-dev libocct-modeling-algorithms-dev <br></br>    libocct-modeling-data-dev libocct-ocaf-dev libocct-visualization-dev <br></br>    libopencv-dev libproj-dev libpyside2-dev libqt5svg5-dev <br></br>    libshiboken2-dev libvtk9-dev libvtk9-qt-dev <br></br>    libvtk-dicom-dev libx11-dev libxerces-c-dev libxmu-dev libxmuu-dev <br></br>    libzipios++-dev netgen netgen-headers pyside2-tools python3-dev <br></br>    python3-matplotlib python3-pivy python3-ply python3-pyside2.qtsvg <br></br>    python3-pyside2.qtuitools qtchooser qttools5-dev shiboken2 swig libyaml-cpp-dev libqt5xmlpatterns5-dev python3-pyside2.qtnetwork<br></br>

In the meantime, I have learned also that I could have created a Fedora 38 container. But now I have Fedora Silverblue 40 as my host OS running a Fedora 39 container and a Debian Bookworm container, so now I am quite the cool kid.

I suppose in a few weeks the whole FC_USE_TNP_FIX will go away, but in the meantime see https://forum.freecad.org/viewtopic.php?p=759223#p751190 to compile with it enabled and experiment.

The build took a while on my i7-1365U system. I never timed it but I think it was over half an hour for a clean build.

azonenberg, to random
@azonenberg@ioc.exchange avatar

Looking for a new Linux image viewer to replace EOG (the default GNOME viewer, which I still use despite now being on XFCE).

Requirements:

  • Can handle large JPEG images (up to maximum 64K x 64K pixel)
  • Allows scrolling/zooming with the mouse wheel
  • Doesn't slow down horribly when running in folders with thousands to tens of thousands of files in them (i.e. https://gitlab.gnome.org/GNOME/eog/-/issues/299)
  • Allows easy left/right navigation through sorted files to quickly flip through a series of frames

Anyone have something to suggest?

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@azonenberg I haven't tested exactly all those characteristics, but have you tried geeqie?

I've been using it since it was gqview, but I don't have your workflow. I think I've used it with a thousand files in a directory, at least.

mcdanlj, (edited )
@mcdanlj@social.makerforums.info avatar

@azonenberg Oh, sorry. I have been satisfied with the default bindings, which meant that my understanding that modified bindings were possible was only theoretical. 😕

mcdanlj, to fedora
@mcdanlj@social.makerforums.info avatar

I decided to try building #FreeCAD from source. I used a F39 toolbox on my #Fedora 40 #Silverblue and installed the prereqs; most from packages, but pyside2 from pip (inside the toolbox) since it hasn't been packaged in Fedora for years. The segfault I'm getting from libshiboken isn't illuminating to me. I could imagine a missing dependency on a package causing a segfault, or maybe no one is building FreeCAD on Fedora and it just doesn't work on F39. 🤔

Not clear that I'm close enough to the beaten path for this to be worth a bug report, though. Quite likely PEBCAK...

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@garrett Thank you.

My only purpose is to try builds from source, running from the build directory, so that I can try things out without waiting for a new weekly build. I use the weekly appimages rather than the flatpak in part because of flatpak moving configuration to not share with native installs.

Because I want to build from git without patches, I'd rather find out what the upstream developers build on, so I can set up a toolbox or distrobox of that particular environment.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@yorik I installed shiboken from distro packages and pyside from pip because it has been dropped from Fedora for not keeping up with Python versions (if I understand correctly).

So shiboken should match system Python, but probably pyside didn't match shiboken.

Is there a Linux distribution and specific version of it that is common for FreeCAD developers? I should be able to install a toolbox or distrobox of it to build and run in. My goal here is to "paddle downstream" by using something similar to you folks who are regularly building current upstream. 😁

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@garrett Yeah, it's the same pyside2 problem I ran into in toolbox. Pyside2 has been dropped from Fedora, I think that was because it's not working on current Python.

I think this is a temporary state, and when FreeCAD moves to Pyside6 along with the Qt6 framework, it will be easier. But that's not going to come before FreeCAD 1.0 I think.

So I think at least currently I'll start from a Debian container since @yorik is using Debian.

mcdanlj, (edited )
@mcdanlj@social.makerforums.info avatar

@yorik Building and running it in a debian:latest container is working, thank you! I used both shiboken and pyside as packaged, not using pip. The current docker build instructions are missing three packages. But one seems to have been intentionally removed, so I just put the information in github for someone who knows what's intended to decide what to do about it.

distrobox create --name debian --image debian:latest<br></br>
trevorflowers, to random
@trevorflowers@machines.social avatar

I want to see a few trustworthy reviews before I have an opinion but if this wire EDM kit works as advertised then it could be ideal for my tiny workshop.

https://youtu.be/lVW18j41Ew4
https://rackrobo.io/

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@trevorflowers If I stop breaking taps then I won't need one for popping tap holes free. 🤔🤪

(I've been doing better recently about this, maybe one in the last year? But it's still tempting.)

mcdanlj, to random
@mcdanlj@social.makerforums.info avatar

I'm happy to see three #Discourse sites I maintain on the new Discourse Discover page:

https://discover.discourse.org/

Want your Discourse community to join the list and help bring in new community members? There's a link at the bottom of the sidebar documenting how to join the party.

mcdanlj, to fedora
@mcdanlj@social.makerforums.info avatar

The #FreeCAD stable build Appimages don't work on #Fedora 40 which is making it hard for me to test a fix I've been working on in the Lattice2 workbench to make it work in current weekly builds as well as stable releases. https://github.com/FreeCAD/FreeCAD/issues/12894 which requires workbenches and macros to be changed.

I'm a novice on Lattice2, so I'd appreciate testing of all the functionality of the workbench both on recent development builds and on stable FreeCAD. I want to make sure that the fix is complete and correct on both stable and development versions before suggesting that it is ready to merge.

If you use git to install workbenches, you can do something like this if you want to test and help:

cd .local/share/FreeCAD/Mod/lattice2<br></br>git remote add johnsonm git@github.com:johnsonm/Lattice2.git<br></br>git fetch johnsonm<br></br>git checkout johnsonm/mkj-attachment-support<br></br>

Feel free to comment on the pull request itself or here, I'll see it either way.

easytarget, to Fonts
@easytarget@social.makerforums.info avatar

Working on a project that uses a small display?

Disappointed by a lack of for them?

Presenting:
https://github.com/easytarget/microPyEZfonts

A hundred fonts in various flavors and sizes, plus a small and simple to use font writer to go with them.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@trevorflowers any possible use in your miniatures?

bricks, to 3DPrinting
@bricks@det.social avatar

Did someone ever try to use a 3D printing pen to fill-in those nasty seam lines that a printed 3D model has on each layer? Usually I sand them away after optionally filling them with super glue and baking soda. I wonder if closing the gaps with a 1.75 mm filament compatible pen could be an option, as I could use the same filament used to print the model.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@bricks Have you tried chucking short pieces of filament in a Dremel or other rotary tool and friction welding over the seam?

I haven't done that for seam hiding but have successfully used it for repair, and it might be easier to control than a pen.

mcdanlj, to fedora
@mcdanlj@social.makerforums.info avatar

I'm on 40, and I'm now seeing a lot of "No video with supported format and MIME type found" errors.

I don't have mozilla-openh264 installed, so I guess that might make sense? Let's fix that...

# rpm-ostree install mozilla-openh264<br></br>...<br></br>error: Could not depsolve transaction; 1 problem detected:<br></br> Problem: package noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System conflicts with openh264 provided by openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264<br></br>  - package openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 obsoletes noopenh264 < 1:0 provided by noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System<br></br>  - package mozilla-openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 requires openh264(x86-64) = 2.4.0-2.fc40, but none of the providers can be installed<br></br>  - conflicting requests<br></br># rpm -qa | grep noopenh264<br></br>noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64<br></br># rpm-ostree install --uninstall noopenh264 mozilla-openh264<br></br>error: Package/capability 'noopenh264' is not currently requested<br></br>

There's clearly something I don't understand here. I don't know how noopenh264 is installed but not requested and still causes a conflict. I must be alone in having this problem based on lack of bugs that I can find in RH's bugzilla.

I don't think I saw this problem on Silverblue 39, but I was using that for only a few days before rebasing on 40, and was previously on my "classic" Fedora 39 installation where it definitely wasn't showing up with the rpmfusion packages installed.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@siosm @swick @adamw @garrett @notting It's definitely not only Firefox. I first ran into this with FreeCAD, as it happened. But it could easily have been anything. Almost everything stores configuration. Why would this be specific to Firefox?

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@siosm @swick @adamw @garrett @notting To avoid mistakes on my part, where precisely on GitHub?

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@siosm @swick @adamw @garrett @notting

it's currently installed in the base image in Fedora Atomic Desktops

That completely ignores everyone who is bringing along a home directory and is following widespread advice to change from native to flatpak.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@swick @siosm @adamw @garrett @notting I would suggest this only when a flatpak app is installed or uninstalled, thus the "source" and "target" language I used. (You might reasonably also suggest a separate capability for users to choose to initiate this at any time if they so desire, but that's not part of what I have been suggesting.)

If the config doesn't make sense to copy for some particular app, then it would be a bug to declare such an equivalence using this suggested feature. But this is not a normal case.

It is not complexly specified, so complexity would be an unnecessary aspect of implementation.

Calling this "little gain" and crudely dismissing it is discouragingly dismissive, and devalues the work that users have done in developing their preferred configuration. ☹️

If it were declared, then at the very least, users could get information in a consistent way about how to preserve their configuration, and not have to hope that they found the right stack overflow answer when they do a web search. The question of whether to automate copying could reasonably be a separate conversation from making a consistent record of equivalent paths for configuration. But the possibility of such a feature could add rationale for implementing the record in the first place.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@swick @siosm @adamw @garrett @notting Let's make perfect the enemy of better shall we? /s

FreeCAD has plenty of paths in configuration. Some of them might not work and still need fixing. It would still be better than starting over entirely from scratch, speaking as a user.

Please feel free to describe specific examples where you feel that this would be damaging so we can have a conversation about specifics rather than sweeping generalities.

mcdanlj,
@mcdanlj@social.makerforums.info avatar

@siosm @swick @adamw @garrett @notting I'm not ignoring this, by the way — my idea is to use this thread of conversation to think through and do a better job of writing up a more coherent feature suggestion.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • provamag3
  • kavyap
  • DreamBathrooms
  • everett
  • magazineikmin
  • InstantRegret
  • ngwrru68w68
  • Youngstown
  • mdbf
  • slotface
  • vwfavf
  • tacticalgear
  • thenastyranch
  • rosin
  • megavids
  • osvaldo12
  • ethstaker
  • GTA5RPClips
  • khanakhh
  • Durango
  • tester
  • normalnudes
  • cisconetworking
  • modclub
  • cubers
  • anitta
  • Leos
  • JUstTest
  • All magazines
    •