

Use saltwater, that’ll work instantly…
I am not a robot. I am a clock.


Use saltwater, that’ll work instantly…
GIMP, Photoshop, Paint Shop Pro, etc all seem to have no problem rendering images with a transparency on top of a checkerboard background layer by default
You know you can layer that transparent image on top of another background, or just simply another solid color. You gotta ask, what is the intent of rendering the image in question?
Is it to render an internal UI component, such as a button or emoji? If so, use the UI background color as the transparency background.
Is it to render an external source image, such as the Wiki post? Then either use whatever background color is encoded in the transparency image, or if that data isn’t available, default the background of transparency images to white.
I see someone doesn’t know how to chase links then.
Just follow the links up the chain, it’s not that difficult.
Innerworld posted that, not me. So yes I’m a bit offended that you got pissy with me, take it up with the original poster, I just had an opinion, and apparently a glitch…
First of all, fuck you, I’m not the original poster. I just shared their link as reference to the problem, which apparently extends way beyond Jerboa…
You might think that someone so fussy about the original source might actually follow the links…
over_clox ≠ Innerworld, the actual OP
This has nothing to do with HTML. This has to do with rendering images, especially when you know your platform will be rendering images that sometimes have transparency.
When you know your app/program/website/platform is going to be rendering images that sometimes have transparency, then the background color is not a fucking option!
The background color behind transparent images should never be connected with the user interface color scheme, the background behind transparent images should always be white.
So this is a long standing problem with UI designers, it ain’t got shit to do with HTML, it’s just that the principles of a good GUI went out the window long ago and GUI developers lost all common sense.
#FFFFFF
Okay, then don’t post anything from Wikipedia, gotcha.
That should fix the problem, thanks for nothing.


I don’t know about TRIM compatibility specifically, but I must suggest you don’t get one of those combo SATA/PATA adapters. Although I don’t know about TRIM compatibility, I do know for a fact that those combo adapters do not support SMART stats for mechanical hard drives. So I assume combo adapters won’t support TRIM either.


I’m just gonna drop this link here…


There’s a music band named Suicidal Tendencies. Can’t even look that shit up online without getting a notice and probably flagged on a list.
Side note, bad name for a band…


Oh, your comment is definitely not an empty comment.
At first I tested tapping the link within Jerboa, no dice. I just got the Invalid Format error.
So, I decided to download the ‘document’ to my tablet, to investigate it. Turned out, it downloaded an HTML file with PDF extension.
In hindsight, it doesn’t inherently seem like a problem with Jerboa, more like a problem with the bait and switch link from justice.gov, swapping a PDF link with an HTML document. The HTML is a script to simply ask if you’re 18 years of age or older.
But the script doesn’t work when force-fed into a PDF reader, which my tablet isn’t even configured for, but Jerboa seems to be forcing it to open a PDF reader, without even giving me the option to open with another app.
Still, especially in the current times, I’m pretty sure that people would like access to these documents, without the file format mistranslation when tapping a link on the screen…


Nope, it’s not even that. My browser (Fennec) is configured to ask every time what app to use, but Jerboa triggering my default browser apparently bypasses that altogether and I never get any option as to which app to load the link/document with.
Other apps don’t do this, other apps give me the option of which app to open stuff with. Jerboa however just blindly goes forward, assuming it sees a PDF, it must be a PDF…


Nope, it’s not even that. My browser (Fennec) is configured to ask every time what app to use, but Jerboa triggering my default browser apparently bypasses that altogether and I never get any option as to which app to load the link/document with.
Other apps don’t do this, other apps give me the option of which app to open stuff with. Jerboa however just blindly goes forward, assuming it sees a PDF, it must be a PDF…


On my Android 11 devices, I don’t have any overall Default Apps menu, I get ‘Open By Default’ in the individual app settings on a per-app basis. So yeah that makes configuring apps extra fun ya know… /s
Either way, Fennec is configured as my default browser, and WPS Office isn’t configured for default anything. Hell, I don’t even use WPS Office, the app is just there as it came with my tablet.


Oh that’s fun, Android 11 doesn’t even have a Default Apps menu…


No defaults even set, it’s Jerboa forcing that.


I’m not the only one, links from justice.gov aren’t working as expected via Jerboa…


Ok. When I copy and paste the link outside of Jerboa, it works just fine and exactly as expected.
But to tap the link here in Jerboa, it finds their HTML redirect shit to ask if I’m 18 or over, but since it’s not actually a PDF document, it errors out and says Invalid Format.
This is NOT an Android issue, this is indeed a Jerboa issue, as I can simply copy/paste the link into a web browser and it just works, as expected.
But tapping the link within Jerboa tries to force-feed an HTML age verification page through a PDF link, which apparently messes up the whole show…


Been there, tried that. No dice, WPS Office isn’t set to default open anything.
Jerboa is apparently forcing that itself.


My default web browser app indeed is already set to Fennec. But that’s not what Jerboa tries to open for web links ending in .PDF
Jerboa is apparently using WPS Office to try to open it, which isn’t even set as a default app for anything in the first place 🤷
Is there any reason you can’t make the model in two separate pieces instead, with the floor and sides as one print, and the roof as another print, to either be glued or clipped together?
I’d think that would avoid the warping problem altogether, plus save wasted filament. Though in all fairness, it would still be nice to learn what’s causing the warping anyways, for sake of future prints…