I heard that Microsoft refuse app's which unreadable in the "night mode" whatever it is? I mean when the phone goes into night mode all the color fonts are changed and that makes app unusable, then they reject the app.
I nave to submit RSS app and I do not know even what I have to watch out about that night mode. Please introduce me.
I suspect that what you mean is "light theme" mode. There are a lot of useful comments about this on this other thread. Windows Phone 7.1 Light/Dark themes management.
From my own personal experience, this is a bit of a headache. If your app isn't very stylistic, try to use the built-in colours for all your controls and whatever you do don't put an image background on it (that was my downfall).
Related
I'm from Ukraine, so I immediately apologize for my crooked English. I got one very incomprehensible problem with which I can not figure it out. I have created a mobile application for Android and IOS. Absolutely normal application. I tested it on the emulator on several phones. But on one of them, the app didn't look like itself. For some reason it became dark and looked strange (I attached the screenshots). The normal version is white-green, this version was dark. I can't figure out what is the reason. Immediately I will say that the phone is normal and the light theme is enabled on it, the phone has standard settings. And everything else on this phone except this application is displayed normally. Please tell me what is the reason
I tried to change the themes and settings of the phone, and found out that the problem is definitely not in them
enter image description here
I'm using opengl es 3.0 API with the android studio ndk to create apps.
But I've encountered a very huge problem. I've created a demo app, all it does it change the background color of the screen from white to black and vice versa, every frame. And so when I go to minimize this app, I still see it rendering the background, mostly at the edges of the screen, and not in full color but still very strongly apparent. And it doesn't go away when I close the app, when I restart the device, or when I run "kill apps" on it. Only a factory data reset fixes the issue, so it's not easy for me to debug this.
This is the relevant code that I'm using for when the app is minimized and receives the APP_CMD_TERMINATE event:
eglMakeCurrent(engine->display,EGL_NO_SURFACE,EGL_NO_SURFACE,EGL_NO_CONTEXT);
eglDestroySurface(engine->display,engine->surface);
engine->display = EGL_NO_DISPLAY;
engine->surface = EGL_NO_SURFACE;
I've error checked that eglDestroySurface() is successful.
And I've put debugging messages in to make sure that the main draw loop is NOT executing when the app is minimized. But the problem persists and I don't know what to do about it. Thanks for any help.
UPDATE: well, no one has responded, and I still don't know what to do. Could it be related to threads?
UPDATE: Still can't determine what it is, but for some reason it's messing with the System UI. Willing to upload my entire source code somewhere if someone would be willing to go through this with me, as I'd really like to be able to continue working on my game engine.
Is it the "Strict Mode" developer option on the device settings, perhaps?
That one flashes the screen if an app is blocking.
It would explain why a factory reset changes behaviour.
The answer is not a solution here. The above comment by the user columbo was correct.
I've demoed switching from black to white at high framerates on 3 different android devices, and also my Linux Desktop, all via the openGL api, and it has exhibited this issue on all the devices. So what he said must be correct: this is a problem with LCD monitor technology itself. Interestingly, doing completely random colors does not cause this problem.
I just heard about this feature on Zoom Meeting and found it a bit puzzling. Do any of you guys have thoughts on how exactly this would work? It seems like window focus isn't something that should be shared by default. Also, it says that the feature only works in their desktop client on windows / mac, so is installation writing some registry changes? If so, any insight on how it works and why it doesn't work on linux?
I'm currently working on a website that will be in an exhibition soon. Users will have a keyboard and mouse in front of them, so I need to lock down the machine to be restricted to just one website. Guided Access mode on iOS is a perfect example. I wish Apple had an OS X version for this reason.
I'm currently trying parental controls but it seems to be quite buggy/not responding to my preferences. I'd really love to just have Chrome or Safari locked to fullscreen somehow so users can't exit the browser/redirect to another website.
Thank you in advance!
I'm thinking you could put Chrome in kiosk mode(can't change website) then change the shortcut keys for exiting out of fullscreen mode if you can on a Mac, and maybe having another desktop and monitor for emergencies. I would have made this a comment but I can't :P This isn't really an answer, just a suggestion. It would really be easier on another OS to do the stuff above.
Recently used 'Web Kiosk' software for exactly this purpose: https://www.macproline.com/webkiosk
It has a lot of options for locking down the machine, both in terms of web sites visited, and disabling key commands, preferences, switching apps, quitting apps, etc.
When searching for a solution for this, I was surprised how few options there were. That said, I would give this a look.
I'm the author of a Windows application that's been around for years. The app uses the wxWidgets UI library. For the newest version, we upgraded to the Microsoft c++ compiler in Studio 10 and to the latest Windows SDK library. We did not change much else in the app. Now, several users have reported that after a period of time running the app, the menus go crazy. All of the users reporting the problem are running on Windows XP. The menus either get huge, filling the screen, and have a giant italic font with strikethroughs. Or they get really small, so that the only thing shown are up and down arrows, suggesting the rendering code thinks the screen real estate is too small to display anything else.
You can find example screen shots here:
Once the menus go crazy, all menus are affected, except the standard Windows and MDI menus. The only way to recover is to restart the app.
The code in the app and wxWidgits is a thin layer on top of the standard Windows API. Once the menus are created, afaik Windows manages the rendering.
Any ideas what's going wrong?