I am working with the Community toolkit, after opening the Popup when I minimize or maximize the window the popup gets closed.
To reproduce the issue please follow the below steps.
Run the attached project.
Click on the button to open the popup.
Minimize and Maximize the window.
See the popup is getting closed.
Get the project from here
Expected behavior:
Popup should not close when the window is minimized or maximized.
Basic Information
Visual Studio: Visual Studio 2022 version 17.5 Preview 1.0
Community Toolkit Version: 2.0.0
Affected Platform : Windows SDK 10.0.19041.0
I can replicate your issue and there is a known issue about this problem.
You can follow it up here: https://github.com/CommunityToolkit/Maui/issues/774.
Thanks for your feedback and patience.
Related
After a recent update for Flutter I found that in Android Studio the package links in stack traces are no longer clickable.
This is not the case with Visual Studio as the links are clickable
Has anyone come across this issue and does anyone know how to fix it?
I'm not a fan of Visual Studio for various usability reasons.
Fixed by upgrading android studio dart plugin to version 213.7371
I am using Visual Studio 2022 Preview where I created a plain MAUI .NET Project. The project runs on Android Emulator properly but the WinUI App doesn't run properly. It shows the message below. But I checked starting project and Debug Settings. Can anyone give me suggestions to run the MyApp.WinUI project on Visual Studio 2022 Preview?
This is a known limitation at this time. Have a look at David's blog post at the end
At the time of release, we are troubleshooting the latest Windows App SDK Single-project MSIX extension for Visual Studio 2022 and .NET MAUI to address a failure to debug. You can successfully deploy the Windows app directly and run it from the Start menu.
From Visual Studio, right-click on your WinUI project and click Deploy. That will make it show up in your Start Menu, you can start it from there. Once started, in Visual Studio you can go to the Debug menu and Attach to Process. Find the process of your app and attach the debugger.
Has anyone else seen F12 developers tool RUN SLOW, Very SLOW on Chrome/Microsoft Edge?
I tried it on FireFox and everything works fine when using F12.
Chrome version: 81.0.4044.129
Microsoft Edge version: Version 81.0.416.68 (Official build) (64-bit)
I reported it via chromium bug report. Just curious if anyone else is seeing this.
I removed a couple of extension and it still does it.
My co-worker figured it out.
https://www.html5rocks.com/en/tutorials/developertools/async-call-stack/
I needed to go to Options for F12 and check "Disable async stack traces".
Once that is checked, F12 developers tool works fine and there is log lag!
Thanks Brad!
I am using android studio 2.3 with window 8.1 my emulator appear for some seconds and after that disppear also genymotion doesn't work appear for long duration with white screen.
To help us repro the issue can you add the following information: https://developer.android.com/studio/report-bugs.html#emulator-bugs
Once you have the info, file a bug here: https://code.google.com/p/android/issues/entry?template=Android%20Emulator%20Bug
I use Unity 4.6.3 and Monovelop 4 is installed by default. It seems Monodevelop 4 has many bugs.
I see the lastest Monovelop is Xamarin(5.9) http://www.monodevelop.com/download/.
Why Unity did't use Xamarin as its default IDE?
If I want to use Xamarin as Unity's default IDE , do you have some tips or document for me.
By the way, I know I can change the default IDE by Edit=>Preferences=>External Tools=>External Script Editor. I just confuse why unity did't use the latest monodevelop?
You're totally right, I've been working with this old and buggy MonoDevelop version way too long.
But there didn't seem to be a real alternative, at least until last week a colleague of mine found some nice Add-Ins, that make Xamarin 5.9 working quite well with Unity.
Note:
This only works for Unity starting from 4.6.5p2.
But I'd recommend to update Unity to the latest version anyway, as there are a lot of bugfixes (especially for IL2CPP, if you're doing iOS).
Add-Ins
The Xamarin Add-Ins can be found here: http://files.unity3d.com/lukasz/Unity-Addins-5.9.0.zip
Requirements
Xamarin 5.9: http://www.monodevelop.com/download
Unity 4.6.5p2 or above:
releases: http://unity3d.com/get-unity/download/archive
patch releases: http://unity3d.com/unity/qa/patch-releases
Installation
Unpack the zip file. You will now have 4 files with an .mpack extension.
Open MonoDevelop/Xamarin Studio.
Open Add-In Manager
OS X: Xamarin Studio ➔ Add-in Manager.
Windows: Tools ➔ Add-in Manager
Click "Install from file" and select the 4 .mpack files.
Restart MonoDevelop/Xamarin Studio.
You should now be able open, build and debug any Unity generated solution/projects.
Make it the default Script Editor in Unity
Open Unity
Go to Preferences (OS X: CMD + ,)
External Tools ➔ External Script Editor
Use Browse to select your Xamarin installation
Source
The complete guide can be found here:
http://forum.unity3d.com/threads/unity-add-ins-for-monodevelop-xamarin-studio-5-9.329880/
you can just set it as default editor. Edit=>Preferences=>External Tools=>External Script Editor
What's problematic is that you can open CSharp Projects in it, but when you have UnityScript projects in your Solution file it won't open correctly in Xamarin. It says could not load project "Your project.unityproj". So Assembly-CSharp* works, but not Assembly-UnityScript*.
That's the reason I can think of so far!