Stud logo preference by trevorsandy · Pull Request #101 · tcobbs/ldview

trevorsandy · 2025-10-30T19:26:34Z

Enable the ability to select stud logo preference using the following stud logo geometry:

0 Plain
1 Single Wire
2 Double Wire
3 Raised Flat
4 Raised Rounded
5 Subtle Rounded

Only the Windows GUI is implemented; however from other platforms (i.e. macOS/Linux), you can set the the following options using [Sessions] in your .ini file.

[Sessions]
LDView Preset - Quality with Edges/UseStudLogo=1
LDView Preset - Quality with Edges/StudLogo=2

This feature is a subset of the comprehensive behaviour which also includes high-contrast studs and edge lines.

With the addition of high-contrast studs and automatic edge line colors, the stud style ini file options have changed to:

[Sessions]
LDView Preset - Quality with Edges/AutomateEdgeColor=1
LDView Preset - Quality with Edges/UseStudStyle=1
LDView Preset - Quality with Edges/StudStyle=2

And stud geometry options are extended to:

0 Plain
1 Single Wire
2 Double Wire
3 Raised Flat
4 Raised Rounded
5 Subtle Rounded
6 High Contrast Plain
7 High Contrast Single Wire

Cheers,

tcobbs · 2025-10-30T20:12:28Z

Did you use LDView's OBI code for the high-contrast work? (I'm guessing not, since it requires modified parts.) The OBI code was added years ago, but never became mainstream due to the requirement of having updated parts.

trevorsandy · 2025-10-30T20:28:40Z

Did you use LDView's OBI code for the high-contrast work?

I did not. The high-contrast behaviour simply extends the primitives in TCStudLogoPrimitive StudLogoPrimitives and adds the ability to manipulate the stud cylinder and edge line colour both manually and automatically. The resulting behaviour adds an 'automate edge line color' checkbox to the Geometry tab and two new options to the Primitives tab's 'use stud logo geometry' combo control:

HighContrast =6 High Contrast Plain
HighContrastSingleWire =7 High Contrast Single Wire

Cheers,

trevorsandy · 2025-11-08T22:35:05Z

I've added the full feature set which includes preference options to manually configure high-contrast studs and edge lines along with the preference to automatically adjust edge line color. The automate edge line color preference is set under the Geometry tab while use stud geometry is under Primitives.

Example model file.

Details

0 FILE StudStyles.ldr
0 Stud Styles
0 Name: studStyles.ldr
0 Author: LPub3D
0 !LICENSE Not redistributable : see NonCAreadme.txt
1 4 0 0 0 1 0 0 0 1 0 0 0 1 3001.dat
1 4 -40 24 0 1 0 0 0 1 0 0 0 1 3001.dat
1 4 40 24 0 1 0 0 0 1 0 0 0 1 3001.dat
0 ROTSTEP END
1 4 80 0 0 1 0 0 0 1 0 0 0 1 3001.dat
1 4 120 24 0 1 0 0 0 1 0 0 0 1 3001.dat
1 15 40 -24 0 1 0 0 0 1 0 0 0 1 3001.dat
0 STEP
1 1 -20 -8 0 1 0 0 0 1 0 0 0 1 subModel-1.ldr
0 STEP
1 15 -60 16 0 1 0 0 0 1 0 0 0 1 subModel-2.ldr
0 ROTSTEP 0 270 0 REL
1 0 100 -8 0 1 0 0 0 1 0 0 0 1 subModel-2.ldr
0 ROTSTEP 0 180 0 REL
1 1 140 16 0 1 0 0 0 1 0 0 0 1 subModel-1.ldr
1 15 40 -64 10 1 0 0 0 1 0 0 0 1 67329.dat
1 71 30 -88 10 1 0 0 0 1 0 0 0 1 15411.dat
1 288 50 -88 10 1 0 0 0 1 0 0 0 1 4070.dat
0 ROTSTEP 0 90 0 REL
0 NOFILE
0 FILE submodel-1.ldr
0 
0 Name: subModel-1.ldr
0 Author: LPub3D
0 !LICENSE Not redistributable : see NonCAreadme.txt
1 1 0 0 0 1 0 0 0 1 0 0 0 1 87580.dat
0 ROTSTEP END
1 14 0 -24 0 1 0 0 0 1 0 0 0 1 3062b.dat
0 STEP
0 NOFILE
0 FILE submodel-2.ldr
0 
0 Name: subModel-2.ldr
0 Author: LPub3D
0 !LICENSE Not redistributable : see NonCAreadme.txt
1 0 0 0 0 1 0 0 0 1 0 0 0 1 87580.dat
0 ROTSTEP END
1 25 0 -24 0 1 0 0 0 1 0 0 0 1 3062a.dat
0 STEP
0 NOFILE

Cheers,

tcobbs · 2026-01-15T23:44:33Z

@pbartfai Do we want to update this PR to support macOS and Qt before releasing 4.7 or after? (Qt for you, macOS for me.)

pbartfai · 2026-01-16T06:27:06Z

@pbartfai Do we want to update this PR to support macOS and Qt before releasing 4.7 or after? (Qt for you, macOS for me.)

Let's release 4.7 first.

pbartfai · 2026-03-17T22:08:25Z

@pbartfai Do we want to update this PR to support macOS and Qt before releasing 4.7 or after? (Qt for you, macOS for me.)

Let's release 4.7 first.

@tcobbs 4.7 has been released
I've prepared the Qt UI...

tcobbs · 2026-03-18T01:19:52Z

Great. I'll do the macOS one. Do you know what the best way is to handle this? I think it's probably easiest to just merge Trevor's Windows-only PR to our master and then create new PRs for Qt and macOS. Note: I have not yet reviewed Trevor's PR, but I will do that. Can you include a Qt screenshot in your PR description? I'll do one for macOS once I have it implemented.

…

--Travis

On Tue, Mar 17, 2026 at 4:08 PM Peter Bartfai ***@***.***> wrote: *pbartfai* left a comment (tcobbs/ldview#101) <#101 (comment)> @pbartfai <https://github.com/pbartfai> Do we want to update this PR to support macOS and Qt before releasing 4.7 or after? (Qt for you, macOS for me.) Let's release 4.7 first. @tcobbs <https://github.com/tcobbs> 4.7 has been released I've prepared the Qt UI... — Reply to this email directly, view it on GitHub <#101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE4BDKKQDDTTMILLWC6KEQL4RHEHBAVCNFSM6AAAAACKWOSG3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANZYGI3TMMBUGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

tcobbs · 2026-03-18T01:47:07Z

@trevorsandy Sorry for the delay. I am finally ready to review this and hopefully merge, but I have hit some possible problems. I'm guessing that this PR includes all of the local changes that you have made to LDView for LPub3d, because there is a bunch of stuff in here that is totally unrelated to the stud logo settings the that PR title makes this seem to be. (You do state in the description that this includes high-contrast studs and edge lines, and maybe that's all that's here in addition to the stud logos.)

While I don't have a problem in principle of incorporating all of these changes, I would greatly prefer if they didn't all show up in one single PR. (Having said that, I am not saying that separate PRs is an absolute requirement.)

How hard would it be to narrow down this PR to just the stud logo changes, and then create one or two other PRs for the other changes? I promise that I will deal with them in a timely manner.

Finally, can you confirm that this PR only contains the following:

Stud logo options
High-contrast studs
High-contrast edge lines
Windows-only preferences UI changes for the above

tcobbs · 2026-03-18T01:48:14Z

After starting to review the PR, I realized that it has two (maybe three) unrelated features. I asked Trevor if he would be willing to split it into multiple PRs. I'll see what he says.

…

--Travis

On Tue, Mar 17, 2026 at 7:19 PM Travis Cobbs ***@***.***> wrote: Great. I'll do the macOS one. Do you know what the best way is to handle this? I think it's probably easiest to just merge Trevor's Windows-only PR to our master and then create new PRs for Qt and macOS. Note: I have not yet reviewed Trevor's PR, but I will do that. Can you include a Qt screenshot in your PR description? I'll do one for macOS once I have it implemented. --Travis On Tue, Mar 17, 2026 at 4:08 PM Peter Bartfai ***@***.***> wrote: > *pbartfai* left a comment (tcobbs/ldview#101) > <#101 (comment)> > > @pbartfai <https://github.com/pbartfai> Do we want to update this PR to > support macOS and Qt before releasing 4.7 or after? (Qt for you, macOS for > me.) > > Let's release 4.7 first. > > @tcobbs <https://github.com/tcobbs> 4.7 has been released > I've prepared the Qt UI... > > — > Reply to this email directly, view it on GitHub > <#101 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE4BDKKQDDTTMILLWC6KEQL4RHEHBAVCNFSM6AAAAACKWOSG3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANZYGI3TMMBUGY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

pbartfai · 2026-03-19T06:06:28Z

Great. I'll do the macOS one. Do you know what the best way is to handle this? I think it's probably easiest to just merge Trevor's Windows-only PR to our master and then create new PRs for Qt and macOS.

The easiest would be merging this PR first then update Mac and Qt code.

trevorsandy · 2026-03-19T06:59:22Z

Hi Travis, I can confirm that this PR only contains the following:

Stud logo options
High-contrast studs
High-contrast edge lines
Windows-only preferences UI changes for the above

I was deliberate to remove content that only implicated LPub3D such as the ability to suppress high-contrast colour management for 'fade previous steps' and 'highlight current step' behaviour.

I'm guessing that this PR includes all of the local changes that you have made to LDView for LPub3d, because there is a bunch of stuff in here that is totally unrelated to the stud logo settings the that PR title makes this seem to be.

There is no code in this PR that is not necessary to implement the behaviour outlined above. If you remain convinced otherwise, I will be pleased to clarify any suspicious code you care to specifically reference.

How hard would it be to narrow down this PR to just the stud logo changes, and then create one or two other PRs for the other changes? I promise that I will deal with them in a timely manner.

There are 7 (essentially 5 with 2 build fixes) commits in this PR. The first 2 commits delineate the stud logo preference behaviour:

Add stud logo dialogue to Windows preferences UI - e1145b3
Add stud logo preference including command line option - ef321d8

...and 3-5 address the manually selected or automatically applied, stud cylinder and edge color management :

Rename stud logo to stud style - f8dcb51
Setup stud style and automate edge line color - 7e3ed83
Setup Windows preferences UI - 2879a1a

As you can see, with the exception of f8dcb51 which transitions naming for better maintainability, these commits are broken down into control logic and Windows UI implementation. This shows that the optimal PR breakdown would create 2 PRs:

Stud logo preference - e1145b3, ef321d8, and f8dcb51
Automate edge line color (introducing high-contrast edge lines and stud cylinder colour management) - 7e3ed83 and 2879a1a

If this breakdown is acceptable to you, I will be pleased to close this PR, and create 2 new ones respectively ?

Cheers,

trevorsandy · 2026-03-19T07:33:03Z

Do you know what the best way is to handle
this? I think it's probably easiest to just merge Trevor's Windows-only PR
to our master and then create new PRs for Qt and macOS.

FWIW, stud logo and edge line colour management was added to LeoCAD, in quite the same manner as this PR. Leo added his change commits to the PR branch until he was satisfied that the content reflected what he wanted - at this point he merged the PR to master. This is also how I manage large updates so as not to implicate the best-so-far state of master until I am pleased with what is being added.

Cheers,

tcobbs · 2026-03-19T20:26:03Z

Do you know what the best way is to handle
this? I think it's probably easiest to just merge Trevor's Windows-only PR
to our master and then create new PRs for Qt and macOS.

FWIW, stud logo and edge line colour management was added to LeoCAD, in quite the same manner as this PR. Leo added his change commits to the PR branch until he was satisfied that the content reflected what he wanted - at this point he merged the PR to master. This is also how I manage large updates so as not to implicate the best-so-far state of master until I am pleased with what is being added.

Thanks for your replies. I can accept leaving this PR alone. It may take me a few days to review all the changes.

tcobbs

@trevorsandy I'm still reviewing, but I wanted to submit the comments on the code that I have so far reviewed.

LDLib/LDPreferences.cpp

LDLib/LDPreferences.h

LDLib/LDUserDefaultsKeys.h

LDLoader/LDLModel.cpp

tcobbs · 2026-03-25T04:46:46Z

LDLoader/LDLModel.cpp

+	if (sm_studCylinderColorEnabled)
+		return input;
+
+	const std::string studColor = "4242";


Given the weird color numbers being used in LDConfig.ldr, how safe is 4242?

LDLoader/LDLModel.cpp

LDLoader/LDLPalette.cpp

LDLoader/LDLPrimitiveCheck.cpp

trevorsandy · 2026-03-26T08:39:57Z

@trevorsandy I'm still reviewing, but I wanted to submit the comments on the code that I have so far reviewed.

Many thanks for sharing these review remarks, they present valuable insight into the architectural and design constraints of LDView that I did not take into account when I implemented this update.

If I may, it would be quite a bit more efficient and productive to reflect your changes as commits to the PR branch. Like this, your preferences and changes will be communicated just as well and we could still discus any changes that require clarification while actually evolving the PR towards what you would find acceptable for integration into LDView.

Cheers,

pbartfai · 2026-03-26T11:15:59Z

If I may, it would be quite a bit more efficient and productive to reflect your changes as commits to the PR branch. Like this, your preferences and changes will be communicated just as well and we could still discus any changes that require clarification while actually evolving the PR towards what you would find acceptable for integration into LDView.

For that we would need permission to push commits to your branch. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

trevorsandy · 2026-03-26T18:25:18Z

If I may, it would be quite a bit more efficient and productive to reflect your changes as commits to the PR branch. Like this, your preferences and changes will be communicated just as well and we could still discus any changes that require clarification while actually evolving the PR towards what you would find acceptable for integration into LDView.

For that we would need permission to push commits to your branch. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

Travis was added as a collaborator on the entire fork many years ago. I sent you an invitation just now.

Cheers,

tcobbs · 2026-03-27T01:11:24Z

OK, sounds good. I'll commit to your branch. Because there as so many changes, it's likely going to take a while.

Co-authored-by: Travis Cobbs <[email protected]>

tcobbs · 2026-03-27T04:13:30Z

@trevorsandy I have committed some fixes to resolve my comments. It would probably be good if you periodically pull and look at the new commits and try to verify that I'm not breaking things.

tcobbs · 2026-03-27T05:54:02Z

Resource.h

+#define _APS_NEXT_RESOURCE_VALUE        550
 #define _APS_NEXT_COMMAND_VALUE         40122
-#define _APS_NEXT_CONTROL_VALUE         1325
+#define _APS_NEXT_CONTROL_VALUE         1357


This is just here to prevent an accidental merge before I get this far.

trevorsandy · 2026-03-27T08:07:12Z

@trevorsandy I have committed some fixes to resolve my comments. It would probably be good if you periodically pull and look at the new commits and try to verify that I'm not breaking things.

I reviewed through 9b7eaf5 and did not see anything suspicious.

I would however like to point out your refactor that adds LDPalette to LDPreferences. I wanted to do this and pondered it for many days, but in the end, was unsure of the full implications so I refrained. Your implementation valades my instinct and it is quite a pleasure to see how you provisioned this update! In fact, your move should solve the different palette load times between the snapshot and interactive modelview flows which could, in certain CLI/snapshot use cases, see the palette initialized before the specified colour parameters were loaded. Well done.

Cheers,

* Remove hard-coded (and edited) LDraw library files. * Load the files from the library on-demand * Algorithmically produce color 4242 versions when needed * Use istringstream to load generated files instead of saving to temp

tcobbs · 2026-03-29T01:34:27Z

@trevorsandy This is a big commit to get rid of the hard-coded stud files and also load the generated strings using a string stream instead of writing files to temp. I tried to test the various code paths, but I may have messed something up. Please give it a try with the various different style options.

trevorsandy · 2026-03-29T09:06:46Z

@trevorsandy This is a big commit to get rid of the hard-coded stud files and also load the generated strings using a string stream instead of writing files to temp. I tried to test the various code paths, but I may have messed something up. Please give it a try with the various different style options.

On a fresh build of the STUD_LOGO branch using StudStyles.ldr (see Details above), the overall behaviour seems as expected:

Automate edge line color seems to behave as expected.
High-contrast edge line color seems to behave as expected.

Here are the exceptions I observed:

Stud cylinder color does not propagate when 'Low quality studs' is enabled (this behaviour was present in the original PR code).
Stud style geometry does not propagate when 'Low quality studs' is enabled (same as above).
Stud cylinder color set to 16 for '7 High Contrast Single Wire'; previously, it would be set to the specified high contrast cylinder color (default 27,42,52,255).
'0 Plain' incorrectly uses primitives with 4242 color code instead of default primitives that use 16. This results in all studs inheriting the 4242 assigned color. (this behaviour was also inherited from the original PR.

0 Plain correction

 if (!sm_studCylinderColorEnabled || sm_studStyle == 0)
 {
 	return;
 }
 const std::string studColor = "4242";

Reload seems to enter a loop, leaving the viewport empty and menu options disabled, under certain flows. I imagine this is repeatable but I haven’t investigated the exact step sequence needed.

Cheers,

tcobbs · 2026-03-30T01:12:05Z

Stud cylinder color set to 16 for '7 High Contrast Single Wire'; previously, it would be set to the specified high contrast cylinder color (default 27,42,52,255).

Just so I'm on the same page. If I enable stud style and set stud style to 7, are the sides of stud.dat supposed to be black?

tcobbs · 2026-03-30T04:56:30Z

@trevorsandy The '7 High Contrast Single Wire' problem you reported should now be fixed. The problem was the presence of 4-4cylc.dat in the library's stud-logo.dat file.

tcobbs · 2026-03-30T05:10:22Z

@trevorsandy Question: are transparent studs supposed to be getting the black sides? That looks very strange to me, but I can see how preventing it might be hard.

trevorsandy · 2026-03-30T06:47:20Z

Stud cylinder color set to 16 for '7 High Contrast Single Wire'; previously, it would be set to the specified high contrast cylinder color (default 27,42,52,255).

Just so I'm on the same page. If I enable stud style and set stud style to 7, are the sides of stud.dat supposed to be black?

Yes - however to be precise, the color should be that which is set as the stud cylinder color. The default stud cylinder color is 27,42,52,255 which is not quite black.

Cheers,

trevorsandy · 2026-03-30T07:04:59Z

@trevorsandy Question: are transparent studs supposed to be getting the black sides? That looks very strange to me, but I can see how preventing it might be hard.

Yes - I pondered making opaque cylinders on trans-clear studs optional using a meta command (in LPub3D) but at the moment, trans-clear studs are opaque. Here is an example:

Cheers,

LDLoader/LDLModel.cpp

tcobbs · 2026-03-31T05:04:47Z

LDViewPreferences.cpp

+	{
+	}


@trevorsandy Is there a reason this is empty?

tcobbs · 2026-03-31T05:04:55Z

LDViewPreferences.cpp

+	{
+	}


@trevorsandy Is there a reason this is empty?

@trevorsandy Is there a reason this is empty?

Yes - there is nothing to do - unlike the void LDViewPreferences::doNewPrefSet(void) function just before.

Cheers,

trevorsandy · 2026-04-02T12:59:44Z

On a fresh build of the STUD_LOGO branch (at ff8d8ea) using StudStyles.ldr (see Details above), the overall behaviour seems as expected:

Automate edge line color seems to behave as expected.
High-contrast edge line color seems to behave as expected.
High-contrast stud cylinder color seems to behave as expected

However, these exceptions remain:

Stud cylinder color does not propagate when 'Low quality studs (Faster)' is enabled (this behaviour was present in the original PR code).
Stud style geometry does not propagate when 'Low quality studs (Faster)' is enabled (same as above).

This behaviour unsettles the UX. I propose that for the GUI, 'Use stud style geometry' and 'Low quality studs (Faster)' should be an either/or selection, with the unselected option disabled to properly indicate the behaviour will not function when the alternate option is selected.
I did not check the CLI behaviour but if it is the same as the GUI then perhaps a console message indicating the contradiction when both options are determined to be enabled would be appropriate.

It is a bit odd that, on reviewing the code, I could not find where the stud style behaviour is ignored when low quality studs is enabled.

Cheers,

trevorsandy added 2 commits October 30, 2025 20:20

Add stud logo dialogue to Windows preferences UI

e1145b3

Add stud logo preference including command line option

ef321d8

trevorsandy mentioned this pull request Oct 30, 2025

Option for choosing which stud with logo to use #100

Open

trevorsandy added 3 commits November 5, 2025 19:25

Rename stud logo to stud style

f8dcb51

Setup stud style and automate edge line color

7e3ed83

Setup Windows preferences UI

2879a1a

trevorsandy added 2 commits November 9, 2025 00:11

Fix 'memcpy is not a member of std' error on Qt 5.15 build

fdc4da5

Fix GCC reorder warning

93cb299

tcobbs reviewed Mar 25, 2026

View reviewed changes

LDLoader/LDLModel.cpp Outdated Show resolved Hide resolved

LDLoader/LDLModel.cpp Outdated Show resolved Hide resolved

tcobbs reviewed Mar 25, 2026

View reviewed changes

tcobbs added 2 commits March 26, 2026 19:33

Initialize new LDPreferences members.

6c06673

Apply suggestions from code review

5bbefe7

Co-authored-by: Travis Cobbs <[email protected]>

tcobbs added 2 commits March 26, 2026 19:59

STUD_STYLE_USE_KEY -> USE_STUD_STYLE_KEY

2f95ada

Don't include LDLib header from LDLoader

2559c3f

Apply suggestion from @tcobbs

9b7eaf5

tcobbs reviewed Mar 27, 2026

View reviewed changes

Clean up stud style code:

79f1ec0

* Remove hard-coded (and edited) LDraw library files. * Load the files from the library on-demand * Algorithmically produce color 4242 versions when needed * Use istringstream to load generated files instead of saving to temp

Don't recolor studs in plain mode

c5d1d90

Fix black sides for standard stud.

507c1a7

tcobbs added 2 commits March 29, 2026 23:06

Fix the last fix

2e7ac06

Get rid of debug printf

ea74744

Finish LDLModel fixes from code review

451398f

tcobbs reviewed Mar 30, 2026

View reviewed changes

LDLoader/LDLModel.cpp Outdated Show resolved Hide resolved

tcobbs added 3 commits March 30, 2026 18:41

Remove no-longer-used macros

90a335f

LDLPalette fixes

db33654

Merge remote-tracking branch 'origin/master' into STUD_LOGO

ff8d8ea

tcobbs reviewed Mar 31, 2026

View reviewed changes

Conversation

trevorsandy commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tcobbs commented Oct 30, 2025

Uh oh!

trevorsandy commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trevorsandy commented Nov 8, 2025

Uh oh!

tcobbs commented Jan 15, 2026

Uh oh!

pbartfai commented Jan 16, 2026

Uh oh!

pbartfai commented Mar 17, 2026

Uh oh!

tcobbs commented Mar 18, 2026 via email

Uh oh!

tcobbs commented Mar 18, 2026

Uh oh!

tcobbs commented Mar 18, 2026 via email

Uh oh!

pbartfai commented Mar 19, 2026

Uh oh!

trevorsandy commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trevorsandy commented Mar 19, 2026

Uh oh!

tcobbs commented Mar 19, 2026

Uh oh!

tcobbs left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tcobbs Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

trevorsandy commented Mar 26, 2026

Uh oh!

pbartfai commented Mar 26, 2026

Uh oh!

trevorsandy commented Mar 26, 2026

Uh oh!

tcobbs commented Mar 27, 2026

Uh oh!

tcobbs commented Mar 27, 2026

Uh oh!

tcobbs Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

trevorsandy commented Mar 27, 2026

Uh oh!

tcobbs commented Mar 29, 2026

Uh oh!

trevorsandy commented Mar 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tcobbs commented Mar 30, 2026

Uh oh!

tcobbs commented Mar 30, 2026

Uh oh!

tcobbs commented Mar 30, 2026

trevorsandy commented Oct 30, 2025 •

edited

Loading

trevorsandy commented Oct 30, 2025 •

edited

Loading

trevorsandy commented Mar 19, 2026 •

edited

Loading

trevorsandy commented Mar 29, 2026 •

edited

Loading