qeed has quit [Read error: Connection reset by peer]
qeed has joined #openscad
<J1A846565>
funny while rendering the aspect ratio looses 3 pixel on y .. maybe the progress bar takes more room
<teepee>
that's the kind of issues that makes actually changing the window size impossible
<teepee>
I'm seeing that with firefox a lot where they try to work around the window management
<teepee>
if it comes back it starts flickering between 2 window sizes and I always have to catch it to make that stop, very annoying
crazy_imp has quit [Ping timeout: 248 seconds]
crazy_imp has joined #openscad
lastrodamo has joined #openscad
ur5us has joined #openscad
<J1A846565>
my windows always resizes the desktop to fullHD when going to sleep mode. Causing some windows to minimize into oblivion .. it is a shame that something so elementary is still not working proper.
<Scopeuk>
J1A846565 monitor "hot swapping" is one of the big improvments claimed in windows 11
<Scopeuk>
it considers monitor configuration when it does window restore/modification and reconsiders it again on change of monitor hotplug status
<J1A846565>
just save for each window the size and pos for the connected monitor .. shouldn't be so hard
<Scopeuk>
yeh the change is mostly driven by laptop users using docks but it equally applies to all hdmi/displayport monitors as they hotplug and enumerate arround sleep states
ur5us has quit [Ping timeout: 255 seconds]
teepee has quit [Ping timeout: 268 seconds]
lastrodamo has quit [Read error: No route to host]
lastrodamo has joined #openscad
ghee has joined #openscad
ghee has quit [Quit: EOF]
ghee has joined #openscad
teepee has joined #openscad
kyki has joined #openscad
kyki has quit [Quit: Leaving]
ghee has quit [Quit: EOF]
SamantazFox has quit [Ping timeout: 252 seconds]
Wolf481pl is now known as Wolf480pl
rvt has quit [Ping timeout: 252 seconds]
rvt has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
teepee_ has joined #openscad
teepee has quit [Ping timeout: 268 seconds]
teepee_ is now known as teepee
pa has quit [Ping timeout: 260 seconds]
SamantazFox has joined #openscad
pah has joined #openscad
califax has quit [Read error: Connection reset by peer]
califax has joined #openscad
ghee has joined #openscad
snaked has quit [Ping timeout: 255 seconds]
ghee has quit [Quit: EOF]
califax has quit [Remote host closed the connection]
califax has joined #openscad
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #openscad
snaked has joined #openscad
hisacro has quit [Quit: \o|]
hisacro has joined #openscad
califax has quit [Remote host closed the connection]
<Scopeuk>
My colleague has a Klein bottle on his desk
<InPhase>
Scopeuk: Or is the desk in the bottle?
<joseph_>
teepee: I've had limited connectivity while traveling these past couple days but I will be online throughout the weekend. So it sounds like an extension of the timeline could still be possible as long as it's done before the final submission window begins? Please let me know what I should do to find out what's involved with this.
<joseph_>
teepee: I thought it would help to see the tasks so far in one spot. GitHub changed their project board feature relatively recently and I'm still learning the new layout. It appears each card can be converted to an issue as necessary. Here's what I've put together so far: https://github.com/users/jbinvnt/projects/1/views/1. Some of these things will definitely need to get taken care of post-GSoC and I can create GH milestones to
<joseph_>
track this
<J1A846565>
Scopeuk if it is on his desk .. it is not a klein bottle (it has a inside and an outside)
rogeliodh1 has joined #openscad
rogeliodh has quit [Ping timeout: 252 seconds]
rogeliodh1 is now known as rogeliodh
<InPhase>
peeps: Yep, I stand by my assertion that stl validation at import would be the most helpful thing for reducing users thinking we have an issue in the code. :)
<InPhase>
I just read the stream of emails that came in today on that.
epony has quit [Quit: QUIT]
<peeps>
yeah, although I wonder if they would still just report the issue anyways and expect openscad to fix their STL, or deny that the STL is bad
<peeps>
or just find some way to misunderstand/misinterpret however we decide to word the warning message
<InPhase>
I'm sure 90%+ would go away. Almost uniformly they report that they concluded the stl was fine because it works before they combine and render something.
<InPhase>
Maybe the other 10% would be "But it works fine in blender." But we can be very explicit in the warning message to ward this off.
<InPhase>
Not just "STL was not manifold" but complete with an explanation explaining it might work in other programs, but setting the right expectation that it won't work in OpenSCAD until it is fixed in a repair tool that can make stl files manifold.
epony has joined #openscad
<Friithian>
``ur stl is shit, go fix it'
<peeps>
maybe add a sad trombone sound effect in there
<Friithian>
``what the fuck is this non-manifold bollucks? Go find a tool built to fix this stupidity, we're here to do stuff that is up to standard!'' :D\