Error adding WrapPanel - xaml

I created a new blank Windows 10 Universal app and tried to add a WrapPanel exactly as per the sample code in the link: WrapPanel XAML Control
I am getting the following error message on wrapPanel:WrapPanel
The name "WrapPanel" does not exist in the namespace "using:Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel"
I have already added xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel" as per sample code.
Full code and errors (please click image for better quality):
I have tried to Clean and Build/Rebuild but it doesn't help. I also made sure that I am targeting the latest Windows 10 version:
Please help!
Update: I tried using xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls"
as suggested but I still get this error. Again, I tried clean and build/rebuild and am getting the a similar error:

The documentation has a typo. The WrapPanel control is not in the Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel namespace, but rather just in Microsoft.Toolkit.Uwp.UI.Controls, so use the following
xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls"
And it should work as expected. I will push an update for the docs.

Related

Tree-View LINKING in Doxygen

In DOXYGEN, initially before Generate_TreeView is checked (i.e, when disabled), when I click on the side function choosing pane, I get the correct documentation of the function. But after Generate_TreeView is checked and when clicked on any function to view its corresponding documentation it shows the File reference instead of documentation. One thing to be noted is : I am generating separate member pages for all the functions.
I got the solution !! Make sure you have checked "SEPARATE_MEMBER_PAGES" in DOXY-Wizard !! I had the following issue in DOYGEN 1.8.4 but once I started using DOXYGEN 1.8.7, the issue got resolved !! Just a version issue !!

Xcode 5 invalid image path error

Im relatively new to programming and am just in the process of uploading my first app to the app store however i am getting the following error message which i just can't figure out / fix. I have looked everywhere online for a solution but as yet, no luck. Please can someone help? I am using Xcode 5:
Error:
ERROR ITMS-9000: "Invalid Image Path - No image found at the path referenced under key 'CFBundleIcons': 'AppIcon40x40'" at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
This really doesn't mean anything to me as i have tried all the usual asset catalogue stuff / looked at my p-list.
You need an App Icon.
If you created the project in Xcode 5 then there should be a catalogue called Images.xcassets where you should place the icons of the correct sizes for your app.
I have added a screenshot of my app as an example of what I am talking about:
I saw the same error. First I thought that the images where not correct (I found one with 144 dpi), but the error showed up again.
Just search for the exact name "AppIcon40x40" in the whole project using Shift+Cmd+F. I have seen it referenced in a plist file under another key. There you have to change the names to the appropriate ones.

pygame2exe "Runtime Error! This application has requested the Runtime to terminate it in an unusual way..."

I've started making a game using python and pygame, and tried using py2exe. It didn't work, (like it should), so I used the pygame2exe code found here: http://www.pygame.org/wiki/Pygame2exe
It still doesn't work, and comes up with the error stated in the title. I have a suspicion it's to do with not having the correct dlls, but I'm clueless apart from that.
Also, I managed to create a pygame executable in what I think was exactly the same way a few months ago, but now it doesn't work. If you'd like me o add a little more info I'd be happy to.
Here's a screenshot of the error message (I can't post images yet):
I've met the same problem and I finally solved it. The problem is with my font definition:
basicFont = pygame.font.SysFont(None, 48)
overFont = pygame.font.SysFont('Comic Sans MS', 60)
Using a default font to replace 'None' in your definition and add '.ttf' files in your dist folder can help

Advanced Custom Fields plugin - potential bug?

Good day,
Does anyone know the solution to the following problem?
I have recently set up the Advanced Custom Fields plugin with a custom post template and have been using Gravity Forms to submit post data. Everything seemed to be working fine on a number of posts. However, I went to update a post through the post editor screen and when I clicked on 'update' or 'preview' I got the following error:
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php on line 396
This was repeated 8 times before the following error code:
Warning: Cannot modify header information - headers already sent by (output started at /home/uswfeoab/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_functions.php:396) in /home/uswfeoab/public_html/wp-includes/pluggable.php on line 876
I have had a good look at the forums and the ACF website but can't find any troubleshooting for errors relating to the _functions.php file. For reference the line of code on line 396 is $field = array_merge($defaults, $field);
Unfortunately this is way beyond my PHP skills. Any suggestions would be greatly appreciated!
Phew!
The author of Advanced Custom Fields issued and update to Version 4.1.2 today. This has resolved the problem.
Panic over!

MVCAwesome, MVC4 and NuGet

I created a new MVC4 project using Razor syntax, and used NuGet to add MVCAwesome.
Looking at this page, it appears that all the expected files and configuration files appear to be in place. I made the edit to the Views/Web.config as directed.
When I try to reference any Awe() controls however, the reference to Awe() shows up in red text, and I get an error message: Cannot resolve symbol Awe()
#Html.Awe().DatePickerFor(model => model.BirthDate).ChangeMonth(true).ChangeYear(true)
Has anyone gotten this to work? What am I missing?
Just FYI, I was able to contact the maintainer of this library. It turns out that in this newer, NuGet version of the controls, you don't need the Awe() part.
For some reason, DatePickerFor still seems to be missing, but I do see other controls there from the package.