Win32 App Can't Render Font/Image Properly - windows

I have this win32 application. I created an installer for it and in my computer it works perfectly fine. I can install and run it. However, when someone I know tried installing it, the application ran but with user interface issues. This is how it looked like. I didn't add the white boxes nor the weird lines. Does anyone of you know the reason why this happened? I have no clue at all T_T. Is there a way to prevent this from happening again? By the way, the UI was made using cocos studio. I'm using cocos2d-x for this app.

Related

I can not see some texts on Unity 3D

In my Unity GUI, some of the texts in the engine can not be seen. I have attached some screenshots from my Recorder and Package Manager. How can i fix this, is there anyone that experienced that kind of glitch?
I am using Unity 2020.3.21f1 on the latest MacOS.
Try restarting unity, and if it does not work, try restarting your pc. Any recently added unity mods might also cause this. Wish you luck!

What is the reason for xamarin app style change?

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

Notifications not working on Windows 10 - Electron JS

I was learning Electron and made a basic electron app and packaged it for windows. The app was not showing notifications so I followed the instructions here
On Windows 10, a shortcut to your app with an Application User Model ID must be installed to the Start Menu. This can be overkill during development, so adding node_modules\electron\dist\electron.exe to your Start Menu also does the trick. Navigate to the file in Explorer, right-click and 'Pin to Start Menu'. You will then need to add the line app.setAppUserModelId(process.execPath) to your main process to see notifications.
I did as suggested here and the notifications started working. They were still working after packaging the app. So I wanted to check whether after a user uses an installer to install this app, the notifications would still work.
I don't have any experience with packaging software, and I used InstallForge to make an installer. Turns out, after installing the app using the installer, the app still works but notifications don't, even after pinning the exe to start.
I tried copying the build folder (direct build, not the installer one) to another location and trying the same thing and it still works. This also works if I copy the installation folder to another location. But it does not work from inside Program Files(x86)\myapp\appname\build\myapp.exe so I am assuming this must be something about permissions, but I do not understand exactly what is happening. I have't checked the app yet on Linux so I don't know if I would face similar problems there as well.
Any pointers would be great, Thank you.

View loading as blank/white screen in Mac desktop application Xamarin.Mac

I have a Mac desktop application developed using Xamarin.Mac and XCode. The application is loading views that should have a considerable amount of content as blank/white screens for a select few end users. While I've not been able to reproduce the issue locally and it doesn't appear to be impacting many people, it does happen consistently for a handful of users(6 out of over 4,000 at the moment). The app works just fine for the vast majority and uses a main window controller that sets the content view as needed by calling the applicable ViewController. When the views in question are loaded for the given users, it renders as a blank white area.
I did notice however that at least some of the objects in the views are actually there, just not visible. For instance, one view has buttons that are still "there" as you can click on them if you know where they are supposed to be positioned(and they also fire correctly) but they are not actually visible as the area is all white with no visible content. It's as if everything is loading properly but the UI just isn't cooperating in displaying objects that are actually there. The closest thing I could find was this Diagnosing run loop issue (partially frozen UI) in Cocoa application
However I'm not sure it's the same problem and there was no resolution for that either. Has anyone else ever encountered something like this?
Ok, got some new info. After doing a remote session with a user we had no luck with the hardware and the console didn't provide much insight, however we did stumble across a workaround that fixes the issue and may give some clues as to the real problem.
When the application is initially installed, we prompt the user to ask if they want it moved to the default Applications directory. They do not have to move it as it will work the same from pretty much anywhere but we do this for convenience. For the users having this problem, we noticed that they all had the app installed in the Applications folder. By sheer luck, one user accidentally chose to not move the app after reinstalling it per our support team. When the app was installed in his default Downloads directory, the problem vanished and the app worked as expected.
After testing various other directory locations(Downloads, Documents, etc.) we found that the issue only seemed to exist if the app was installed in the Applications directory. Furthermore, if the app was installed in the Applications directory, we could simply move it or copy/paste it to another directory outside Applications and when launching it from that new location the issue was resolved.
Seems like there is something specific to the default Applications directory that is causing this to happen(as odd as that sounds). Keep in mind that even when the app is installed in the Applications directory, this issue only happens to 7 people out of over 4,000.
Any ideas as to what might be special about that directory that could explain what we're seeing?

The parameter is incorrect exception

I'm working on a Windows Phone 7.1 project and got most of my work done and decided to add to the project the images for my tiles (62x62 and 173x173 PNGs) plus the JPG file for the splash screen (SplashScreenImage.jpg 480x800).
Before adding these images to the project my project was running fine! After adding them and setting the tiles images to the 2 new files, my project still builds ok, but when running on the 7.1 simulator (my acer laptop doesn't have hardware assisted virtualization enabled in order to run the wp8 emulator) the app crashes when trying to load MainPage with "The parameter is incorrect" exception (in the Application_UnhandledException handler).
I've been trying to find a solution on the web for the last 1-2 days, found few mentions of this error and few possible causes, but none of my findings helped so far. The exception doesn't say anything helpful and it's getting really frustrating considering that most of the serious work is done and I'm very close to releasing the app to the marketplace.
Did anybody run into this issue before? Any ideas what could have gone wrong and how I could solve this exception? Any help is much appreciated!
Thank you in advance!
Andrei
Whenever I wish to change the Splashscreen and other images, here is what I do:
Locate the file on disk using Windows Explorer.
Open the file using some image editor (I use Paint.NET)
Remove the default image and replace with your image maintaining the dimensions.
Save the image and return to Visual Studio.
Rebuild the entire project.
This works seamlessly without any errors. ;)

Resources