Can we better document what the different parameters for Progress Printer's constructor mean?
https://cntk.ai/pythondocs/cntk.utils.html#module-cntk.utils.progress_print
This as been fixed. The documentation site will be updated with release 2.0 beta 8 or greater.
Related
I'm currently trying to upgrade a custom app from sdk 1.x to new version 2.0rc3. I saw the Task Board app or Custom Board app in the AppCatalogs have ability to group the tasks by WorkProduct, however I have unable to make it work.
I have copied/pasted exactly the given example here and it does not work also.
In the screenshot from this link: https://rally1.rallydev.com/apps/x/doc/#!/example/groupable-board
it shows the cardboard grouped by the owner but when I try it, cards item is not sorted into group as expected.
if anyone know how to make it work, please help me.
Thanks!
The swimlanes feature that rowConfig enables is not available in 2.0rc3. The version x SDK and documentation are not officially released, but we will be releasing a new 2.0 version early in 2015 which will definitely include support for this feature.
In the meantime you can use /apps/x/sdk.js to build apps with the usual caveat that this is not a stable version of the API yet and we make no guarantee that any apps written against it will continue to work.
I've checked through glGetString(GL_EXTENSIONS) that my OpenGL ES 2.0 implementations did not support GL_OES_vertex_half_float and OES_element_index_uint. I'm using MALI 400 MP. Are there any way to restore both of them?
Thanks
It is not possible to "restore" an extension. If the extension is not included in the string returned by glGetString(GL_EXTENSIONS) it means that the OpenGL ES driver does not support that particular extension, so the feature is not available.
So on your current device / drivers you're out of luck, I'm afraid.
You could try to request that the driver vendor adds support for these extensions in the future; for Mali, try these forums. But, of course, there may be HW limitations that prevent certain extensions from being supported.
My C# app uses a C++ WinRT component I've written to get a list of system fonts using Direct X.
This is based on this example:
http://msdn.microsoft.com/en-us/library/dd756582(v=VS.85).aspx
My app is published in the store, but my latest update failed to pass the store review process on point 3.10 complaining about my use of Direct 3D and how this might not run on ARM tablets. As far as I know I'm not using Direct 3D and the only Direct X feature I'm using is GetSystemFontCollection.
How can I make sure I don't fail this requirement and do I need to remove some rogue reference in my component to Direct3D?
Also, why am I failing this now, when it passed before?
Did you target all three platforms or choose any cpu in your release?
Does this page help:
http://msdn.microsoft.com/en-gb/library/windows/apps/hh994923.aspx
It looks like you may have inadvertently requested a higher level.
I submitted again and included a note to the tester explaining that my app didn't use any Direct 3D features, and I told them the exact DirectX function I did use.
I still failed, but the Direct3D reason was no longer one of the reasons.
Apparently my app is crashing, which was another failure reason the first time round, but I thought this must be related to the Direct3D problem. I can't reproduce the crash, but at least I now know that I can stop looking at my use of DirectX. This was a red herring.
In iOS 5 and above, Apple introduced the ABPersonCreatePeopleInSourceWithVCardRepresentation method, which is pretty useful in feeding a vCard to the Address Book and getting back the ABRecordRefs for the persons created.
However, the Apple vCard seems to be (at least a bit) different from a standard vCard, as I have found out while trying to add standard vCards to the Address Book. Is there a page somewhere detailing what the Apple-format for a vCard should be?
Thanks!
The ABPersonCreatePeopleInSourceWithVCardRepresentation docs state that vCard version 3 is the supported protocol. Unfortunately if you're having troubles with a standard vCard I'm not sure how to help - I did a fair bit of searching (that bounty is good motivation :P) and wasn't able to find any further information.
I don't have my iPhone on me to test, but this guy claims to have successfully imported the following, v2.1 vCard on an iPhone 4 using a QR scanner app (which might be using the API in question). The 3.0 spec is a superset of the 2.1 spec - can you try this vCard and let me know if it works?
BEGIN:VCARD
VERSION:2.1
N:;Company Name
FN:Company Name
ORG:Company Name
TEL;WORK;VOICE;PREF:+16045551212
TEL;WORK;FAX:+16045551213
ADR;WORK;POSTAL;PARCEL;DOM;PREF:;;123 main street;vancouver;bc;v0v0v0;canada
EMAIL;INTERNET;PREF:user#example.com
URL;WORK;PREF:http://www.example.com/
NOTE:http://www.example.com/
CATEGORIES:BUSINESS,WORK
UID:A64440FC-6545-11E0-B7A1-3214E0D72085
REV:20110412165200
END:VCARD
You can read the official 3.0 spec here and here.
As a last ditch solution, there are plenty of vCard parsers out there - it's a dead simple protocol. You could just take any of these (or write one yourself) and manually add the contact to the Address Book using ABPersonCreatePeopleInSourceWithVCardRepresentation.
I've created a backwards compatible VCard class, that generates .vcf files. But for iOS devices < iOS 8, the class exports to .ics files (VCards are then wrapped in a VCalendar file) because thats the only way to get things working on older iOS versions!
Used by thousands of people! Check it out on GitHub
Since iOS 9 / iPadOS 9 / watchOS 2.0 / macOS 10.11 you should use the Contacts framework instead with the formatter class CNContactVCardSerialization documented at
https://developer.apple.com/documentation/contacts/cncontactsuserdefaults
Unfortunately, i no longer see a mention of the vCard version(s) that are supported.
I am building my app using iOS 5.0 as base SDK and iOS 3.0 as deployment target.
I know I need to check for existence of methods and classes when I work with features that are not available in the earlier iOS versions, but lately I've lost a few hours on a problem just to discover I was calling a method not available in some iOS versions. I simply did not notice it was a new method and did no check before to call it. The app of course compiled with 0 errors and 0 warnings.
This is a big problem because if I forgot some other check somewhere in the app, I will not know it until I or, worst, some user will activate that specific part of code.
Maybe I am missing something, is there some compiler option I can set to detect the calls I make to methods not available in the iOS deployment target? How do you deal with such a problem?
This link might point you in the right direction. Supporting mutiple ios Versions in your apps. It explains how to deal with taking advantage of the newer ios features while maintaining backwards compatibility. Hope that helps.
The only way to check for compatibility with a prior version of iOS, currently, it to test the app on an old non-updated device running that version of the OS.
If you can't find a device that old, even just to borrow for short time, then there may not be a good buiness reason to set the Deployment target that low.