I am working on Anywhere development, Is it possible to use the Real and electronic signature features in current code base version 7.5.2.0 ?
Unfortunately it's only available in 7.6 and higher releases.
Related
Both have their own documentation and I see only small wording differences between those. Are there list of things that have actually changed? Has OCR for example improved on version 2.0 or it's the same except I guess the handwriting recognition? Some kind of changelog would really make a difference.
The only difference between v1.0 and v2.0 is the revised /recognizedText which has a breaking change in the input/output. All other endpoints are exactly the same. Also, if you have an key in an up-to-date pricing tier (including free), your API key will work in both versions.
As you may know, the Computer Vision API has two different OCR endpoints. The /ocr endpoint runs the older recognition engine with broader language coverage. The newer /recognizeText endpoint, which in v1.0 handled handwritten text, in v2.0 covers both handwritten and printed text using a newer engine. The /recognizeText endpoint remains English-only for now. You select between handwritten/printed modalities using the mode query parameter. See
documentation here.
As for documenting changes, there isn't one obvious place for this unfortunately. One option is to check the swagger repo.
I'm developing an application that makes use of Qt and OpenGL, using Qt Creator and QGLWidget subclassing.
My application has a user base that has a higher than average proportion of older hardware, which is why I need it to run on machines with graphics cards supporting OpenGL 2.1 only - or, in other words, I cannot rely on anything newer than 2.1 being present.
I am worried about unknowingly using OpenGL functionality that was introduced after 2.1. Is there any way I can configure OpenGL to "only" support 2.1, so that I would get a runtime error if I do something I shouldn't be doing? Or, failing that, what is the best practice to ensure compatibility?
The only thing you need to worry about is not creating a OpenGL-3 core profile context, and only to use functions found in the OpenGL-2.1 specification.
Since creating a OpenGL-3 core context requires you to jump some hoops, you're not running into problems there. The system may give you something newer than OpenGL-2.1 but as long as you don't use any functionality not found in the 2.1 specification document you're fine. You'll have to use the extension mechanism, to actually get the functionality on Windows; OpenGL-2.1 is technically a list of extensions made official functionality, so carefully read the Appendix of the specification, where the functionality that formerly were extensions are explicitly mentioned.
I have downloaded OpenMHeg simulator..how to develop an application in mheg?what eclipse version i need to use?where do i get the sdk for mheg?
I haven't tried yet. but I think it's worth trying. Someone said that the BBC's implementation of MHEG5 is open sourced
It can be downloaded from mhegplus on sourceforge
There is no MHEG-5 SDK. There is some limited documentation available online, and a few discussions of the type hierarchy.
Since MHEG-5 has no support for user defined types and the API is completely provided by the implementation (in various states of brokenness), you only need an editor and an understanding of the application model to write applications.
I wrote an introduction to MHEGPlus a while ago but didn't go into any advanced application building techniques. There are a few more examples out there if you look for them.
We are using Adobe LCDS 2.1 and thinking of Upgrading it to a higher version.. can someone tell me a brief Comparison of the LCDS versions available (3.1 , 4.1....) ????
The last version is 3.1 You need to read the documents from this url in order to understand what are the new features (the release is good but is not enough), and after that it would be good to try building a prototype (if you plan to use the data modeling for example) to see how they will fit into your current architecture.
I wouldn't do any upgrade unless there is a business reason (bugs, poor performance, luck of productivity) - for any product.
I don't know why you'd need a comparison for 'all versions' if you can only purchase the latest one. I suggest you look at the latest version's whitepaper so that you can see what's been added. The biggest thing IMO is better integration for all clients, different messaging protocols and well as much needed bug fixes (I remember 2.1 had some fairly obvious bugs).
Looks like the choice is "should we upgrade or not?"
I'd say it may also be worth considering what you're doing with LCDS -- if you're only using it for things like Flash Remoting, is it possible that you could go the other route and 'downgrade' the the open source BlazeDS? It has a lot fewer features, but might do what you need, and be a lot cheaper.
Here's a comparison of BlazeDS to LCDS ES2: http://www.adobe.com/products/livecycle/dataservices/compare.html
I'm not familiar with prior releases of LCDS, so I can't offer any better advice about comparing versions than the previous respondents. Basically: Check the release notes =)
According to http://msdn.microsoft.com/en-us/library/aa916070.aspx (DnsQuery_W), DNS query libraries are available on Windows Mobile / CE developers for versions 5.0 onwards. Yet, "#include " gives nasty "file not found" errors. What gives?
Strangely enough "dnsapi.lib" is available. Does Microsoft actually expect developers to scavenge the file from somewhere?..
The posted thread here claims that this API is not actually available in Windows Mobile 5 (and perhaps later?), despite claiming otherwise. I looked through the Mobile 5 and 6 SDKs, and didn't see this API either, so perhaps the thread's suggestion might work for you:
If it's a simple host name->IP address
(IPv4 or v6), you can use getnameinfo
in Winsock. The DNSQuery_W is only
needed if you're doing like a
non-A/AAAA query. If you're doing
that, we really don't have any helpers
to do that for you from the OS side -
sorry. You may look around to see if
there's helper library floating around
out there that you may be able to
recompile for CE (assuming you're
comfortable with whatever licensing
agreements they may put on you.)
getnameinfo should be documented here (for Windows Mobile), in case that helps.
If you are really after 'windns.h', I found it in the WM5/WM6/WM6.1 Platform Builders in
\public\common\sdk\inc
The hard part is getting access to the WM Platform Builder if your an ISV. That I can't help you with.