doki-theme-jetbrains: Sticker do not display properly

I found that the UI element of the sticker intercepts click events and the drag and drop function works fine, but the whole element is completely transparent.

I see the following in the output at startup:

2021-08-29 05:17:55,713 [   1233]   WARN - tor.impl.FontFamilyServiceImpl - Couldn't access required runtime API, will fall back to basic logic of font selection
2021-08-29 05:17:56,510 [   2030]   WARN - rottled.doki.hax.HackComponent - Unable to hackSwitcherBorder for reasons.
2021-08-29 05:17:56,549 [   2069]   WARN - rottled.doki.hax.HackComponent - Unable to hackBookMarkBorder  for reasons.
2021-08-29 05:17:56,669 [   2189]   WARN - rottled.doki.hax.HackComponent - Unable to hackLivePreview for reasons.
2021-08-29 05:17:56,713 [   2233]   WARN - rottled.doki.hax.HackComponent - Unable to hackBookMarkBorder  for reasons.
2021-08-29 05:17:56,717 [   2237]   WARN - rottled.doki.hax.HackComponent - Unable to hackWelcomeScreen for reasons.
2021-08-29 05:17:56,748 [   2268]   WARN - rottled.doki.hax.HackComponent - Unable to hackLivePreview for reasons.
2021-08-29 05:17:56,758 [   2278]   WARN - rottled.doki.hax.HackComponent - Unable to hackSwitcherSelection for reasons.
2021-08-29 05:17:56,762 [   2282]   WARN - rottled.doki.hax.HackComponent - Unable to hackTipBorder for reasons.
2021-08-29 05:17:56,765 [   2285]   WARN - rottled.doki.hax.HackComponent - Unable to hackCaptionPanel for reasons.
2021-08-29 05:17:56,781 [   2301]   WARN - rottled.doki.hax.HackComponent - Unable to hackPopupBorder for reasons.
2021-08-29 05:17:56,785 [   2305]   WARN - rottled.doki.hax.HackComponent - Unable to hackStatusLineColor for reasons.
2021-08-29 05:17:56,787 [   2307]   WARN - rottled.doki.hax.HackComponent - Unable to hackColors for reasons.
2021-08-29 05:17:56,791 [   2311]   WARN - rottled.doki.hax.HackComponent - Unable to hackSdkComboBox for reasons.
2021-08-29 05:17:56,793 [   2313]   WARN - rottled.doki.hax.HackComponent - Unable to hackDebuggerAttributes for reasons.
2021-08-29 05:17:56,794 [   2314]   WARN - rottled.doki.hax.HackComponent - Unable to hackDebuggerAttributes for reasons.
2021-08-29 05:17:56,796 [   2316]   WARN - rottled.doki.hax.HackComponent - Unable to hackDebuggerAttributes for reasons.
2021-08-29 05:17:56,799 [   2319]   WARN - rottled.doki.hax.HackComponent - Unable to hackSwitcher for reasons.
2021-08-29 05:17:56,831 [   2351]   WARN - rottled.doki.hax.HackComponent - Unable to hackTitleFrame for reasons.
2021-08-29 05:17:56,835 [   2355]   WARN - rottled.doki.hax.HackComponent - Unable to hackTestResults for reasons.
IntelliJ IDEA 2021.2.1 (Community Edition)
Build #IC-212.5080.55, built on August 24, 2021
Runtime version: 16.0.1+9 amd64
VM: OpenJDK 64-Bit Server VM by AdoptOpenJDK
Windows 10 10.0
GC: Shenandoah Pauses, Shenandoah Cycles
Memory: 16384M
Cores: 32
Registry: ide.intellij.laf.enable.animation=true, debugger.watches.in.variables=false, ide.tooltip.initialDelay=0, ide.balloon.shadow.size=0
Non-Bundled Plugins: io.acari.DDLCTheme (18.0.0), amadeus.maho (212.5080.55)
Kotlin: 212-1.5.10-release-IJ5080.55

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

By the way, if you have any doubts about Chinese, you can ask me.

Yes, my library can do a lot of black magic.

Magic

You change the parent class from HwFacadeJPanel to JPanel if you wish to be OpenJDK compatible.

I’ll probably do something along the lines of that later, so will leave this open for the time being.

Also should I care about HackComponent’s failure?

No, most of were created to change things like hard coded colors and stuff. I should probably go back and clean some of those up later in the future.

So I take it amadeus.maho (212.5080.55) allows you to do crazy things like overriding methods, such that you can provide your own implementation as a work around?

Yes, my library can do a lot of black magic.

If so, do still want a fix? (Thanks for doing most of the investigation by the way!)

It doesn’t seem to matter at the moment, and in any case I’m free from this problem for the time being. This should count as an IntelliJ issue.

You change the parent class from HwFacadeJPanel to JPanel if you wish to be OpenJDK compatible.

Also should I care about HackComponent’s failure?