Running Without Transparency

[andrewauclair]

This is running a Modern Docking app remotely on CentOS 7 through MobaXTerm. Looks like I finally found a setup without transparency to use for testing. I'm not sure what to do in this case. Perhaps the docking handles are only supported when transparency is available.

[tlf30]

Hmm, I guess I have not run into this issue. Would it be possible to draw the handles without transparency in this situation?
I would have to look into the code. I imagine that it would be difficult and a complete change in how the handles are drawn just to accommodate this.
I personally am not having this issue, but I imagine that at some point I will run into it since I so run my apps on multiple linux systems. I guess I am usually running in headless mode when I run my apps on linux though.

EDIT: Or perhaps this is an issue in MobaXTerm that needs to be reported to them so they can fix it.

[andrewauclair]

I didn't really have a plan for what to change or how atm. It was just interesting to finally find a setup where the setup/system didn't support transparency. I knew this was an option when I was configuring the windows a while ago. I would like to understand better why it happens. It's either a limitation of displaying remote UIs or a setting to save bandwidth/performance.

[seclerp]

Hi! I'm trying to get started with ModernDocking on a fresh project from scratch, and I'm getting this weird behavior on Windows, a black box once I'm detaching the tab from the main window and trying to dock it somewhere else. Am I missing some configuration?

[andrewauclair]

Hi! I'm trying to get started with ModernDocking on a fresh project from scratch, and I'm getting this weird behavior on Windows, a black box once I'm detaching the tab from the main window and trying to dock it somewhere else. Am I missing some configuration?

Do you have a minimal example that you could share that shows the issue?

[seclerp]

@andrewauclair thanks for a quick response. The problem reproduces for me even on demo-single-app project. I use Windows 11 without any disabled UI capabilities.

[seclerp]

It was tricky to get the screenshot, but here you go:

[seclerp]

I've tried to debug the demo code and can assure that setOpaque(false) gets called as expected without any exception:

ModernDocking/docking-api/src/io/github/andrewauclair/moderndocking/floating/FloatUtilsFrame.java

Lines 157 to 165 in a0b2d2d

	if (getContentPane() instanceof JComponent) {
	((JComponent) getContentPane()).setOpaque(false);
	}
	}
	catch (IllegalComponentStateException e) {
	// TODO we need to handle platforms that don't support translucent display
	// this exception indicates that the platform doesn't support changing the opacity
	}
	}

[seclerp]

Seems like I found the problem - I've used JetBrains Runtime 21 with the demo and my project, switching it to another one (Microsoft OpenJDK 21 in my case) solved the problem. Seems like JBR doesn't handle transparency correctly.

[andrewauclair]

Interesting. I tried it out and I am seeing the same behavior.

[seclerp]

Hi! Possibly related? #351

[andrewauclair]

The changes for #399 should address this issue. Or a second refactor after that to allow some automatic detection of bad transparency.