Forum Replies Created
-
Posts
-
This keyboard depends on flag “Console mode”. Probably you enabled “COnsole mode” on Welcome screen. You can disable it from main menu
And maybe you will like new option in advanced setting – background texture
I am happy that this thread leads to cool feature, maybe one day I will write book about designing games in mDosbox, LoL
Yes, if game has “natural” border then this is currently best way. I added streaming to foreground and in this case is possible set standard widget’s background. But this means that due tiny border is created and drawn big background texture. I’ll make optimizations in v54 together with layers support, but still will be efficient streaming to background instead streaming to foreground(only background from pure color – picked from color picker will be none problem).
Ou, now I am very curious. Can I contact you via email please? But tomorrow. Now I must go sleep, but I am aware that more people can have the same issue. I like to fix it, but I must send you more test versions…
Ok, I see your crash report. Your device has problem with loading native c++ library(probably, there is Uknown source line, but UnsatisfiedLinkError talks about problem with loading c++ library ). That’s weird.
java.lang.UnsatisfiedLinkError:
at java.lang.Runtime.loadLibrary(Runtime.java:367)
at java.lang.System.loadLibrary(System.java:1076)
at magiclib.collection.CollectionActivity.init(Unknown Source:0)
at bruenor.magicbox.free.uiGameStarterActivity.onCreate(uiGameStarterActivity.java:61)You must have trouble with other programs too. I’ll try google, but I don’t see any reason why native lib should not be loaded.
EDIT:
Please can you try this version :
https://magicbox.imejl.sk/wp-content/uploads/sharedata/MagicBox_v53-debug.apkthis is unaligned free version. This means that strings inside application are not packed. Maybe it affects library name and this causes problems with loading.
If possible, could you send crash report from this beta application? Maybe it will not work, because you didn’t download it from google play. But it can explain what hides behind “(Unknown Source:0)”. If it will not work then I can add you to group of testers for free version and you can download it from google play
No nothing yet. Google rewrote arn&crashes page and they removed quick crash report notification. Now I must navigate through 2 submenus to get to fresh crash reports. But I don’t see nothing new. Crash and report is now trashed to more pages and is not very intuitive. On each page I see generated report from date to date. Each date ends with 13.6.2017, seems google play generates reports to one day behind. So wait to next day, hope the report will arrive.
But this crashing is really weird, two things come on my mind :
1. Your device may have trouble with access to root internal storage. In this case Magic Dosbox can’t create core files and folders and will crash.
2. Your device does not like PopupWindow (welcome screen) what appears after each installation.For both points I can make test applications, but let’s wait first to next day, hope your crash report will arrive.
Hmm, I don’t receive any crash report in last 7 days…please, can you send it again? Make sure your internet connection is on…Do you experience similar crashes with another applications?
Hi, thanks for report, usually phone offer send crash report to google play. Do you see this option?
And when it crashes? Magic Dosbox has two parts, main menu and game. Starting which part crashes?
And do you have latest version from google play? What is your device for?
But, that’s what I was talking about. Deadly strike/Combo has action for setting absolute/relative mouse at startup.
Press on action for settings, default is toggle
Thanks for ideas. Something for multiple layouts is in progress. Unfortunately not for layouts but layers. But this could be good fix until multiple layouts will be not developed. This feature should go out in one of next versions, currently biggest problem is user interface implementation, core functionality is done.
Yes, Alex is right. Another option is to create deadly strike widget with relative/absolute action. You can bind it to “Run at start”. Only one widget can be fired at startup, so if you need multiple actions then you must add them all together
This is not a problem. I can add option for that to ZoomWidget.
One thing what you can’t do with current implementation is that white border around characters, because I stream to widget’s background. This is the efficient way. Solution is streaming to foreground and you can setup background. This is not efficient way, because people will create big background textures (with current implementation) – and only because they need tin border. If your background will be pure color then I can fix it easily, opengl does it fine. for images I can do partial fix, but it will work fine.
