You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In OSXAdapter, the image used for the macOS dock icon is being downloaded dynamically from RPTools.net and then cached for future use. It's using an http:// scheme that seems to fail in Eclipse (but works elsewhere), but we should be populating the JAR with this file instead and referencing it from there.
To Reproduce
Steps to reproduce the behavior:
Start MapTool within Eclipse on macOS
Note the exception from the PNG not being downloaded and the dock having the generic "Java" logo
Expected behavior
With the logo embedded, the image should always be available.
MapTool Info
Version: latest develop branch (1.5.7)
Install: None (Eclipse build)
Desktop (please complete the following information):
OS: macOS only
Version macOS Mojave 10.14.6 (although I believe not OS version dependent)
Additional context
No idea why this wasn't embedded into the JAR years ago. :(
Once cached, the name is referred to as maptool-dock-icon.png so we should probably just name it that in the JAR and refer to it the same way...
The text was updated successfully, but these errors were encountered:
Describe the bug
In
OSXAdapter
, the image used for the macOS dock icon is being downloaded dynamically from RPTools.net and then cached for future use. It's using anhttp://
scheme that seems to fail in Eclipse (but works elsewhere), but we should be populating the JAR with this file instead and referencing it from there.To Reproduce
Steps to reproduce the behavior:
Expected behavior
With the logo embedded, the image should always be available.
MapTool Info
develop
branch (1.5.7)Desktop (please complete the following information):
Additional context
No idea why this wasn't embedded into the JAR years ago. :(
Once cached, the name is referred to as
maptool-dock-icon.png
so we should probably just name it that in the JAR and refer to it the same way...The text was updated successfully, but these errors were encountered: