Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DesktopAssetManager bad naming
See original GitHub issueDesktopAssetManager is a misnomer. It’s included in jme3-core and used both on desktop and mobile platforms.
What about renaming it to DefaultAssetManager?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
IT Asset Naming Conventions: Why You Need a Name ... - Blog
There are many factors in keeping your asset management practice organized. One of them is making sure your assets are all properly named....
Read more >Computer Names | Asset Management Suite
I'm looking for input for computer naming conventions. ... What you have above isn't bad, but doesn't take into account multiple computers in...
Read more >Fix issues in Fixed Asset Manager (FAM) - QuickBooks
Right-click the old Accumulated Depreciation account and select Edit Account. Remove the number that you added in the account name and select Save...
Read more >Incorrect Computer CI being associated with Hardware Asset
We are seeing an issue where incorrect Computer CI's are being assocaited with Hardare Assets. This appears to be occuring when the computer...
Read more >Practical Solutions for Poor Asset Management - ManagerPlus
Learn about the most common problems with poor asset management and ... An asset naming convention defines how you refer to your assets...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Technically it’s nice to deprecate things first. Otherwise, what you end up with is just people using 3.3 forever and never upgrading because “it breaks a bunch of stuff and I don’t have time to fix it all at once”. Nicer if they can deal with some warnings over time.
Plus, this is a “we just don’t like the name anymore” issue… which we decided in a few minutes without looking back at the history to make sure it’s even correct. Maybe it’s a bug that android is using DesktopAssetManager now? I’d have to do a lot more research personally before I was willing to rubber stamp this change because my memory says different things than the reality that I’m being presented.
There is no technical reason to change other than a little confusing for folks diving in deep.
I tested and debugged this today, and fortunately it didn’t show up a reflection call problems, i have looked back to android developer docs and it seems i have interpreted somethings wrong, sorry, it’s my fault, you can continue your discussion here or on forums, i have no anticipated android changes for this.