I developed the Lync conversation extension window to Lync 2013 client that used silverlight.
I want to resize the extension windows size and set the registry key "ExtensibilityWindowSize"=dword:00000000.
But the small size(dword:00000000) and medium size(dword:00000001) are same size and identity.
How can I set ExtensibilityWindowSize to small in Lync 2013 correctly?
It seems that size 0 and 1 are identical despite the advertised values on MSDN.
Source: http://blog.thoughtstuff.co.uk/2012/12/lync-conversation-window-extension-cwe-sizes/
Related
I'm currently working on a project consisting of one program which tracks faces (which we got from https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/BasicFaceTracking), which is a Windows Universal App and our program, which is supposed to get the number of faces recognized and reacting appropriately.
I thought about copying the number of faces detected by the facetracking program to the clipboard and just reading it from the program.
The problem I have (which might actually be really simple) is that I can't seem to get to the Clipboard Class from within the UWP app.
Using OpenClipboard(NULL) or similar but I always get the error that the IDentifier is not found, no mater which header I include or not...
Can anyone give me a clue what to do? Or maybe a better alternative to transfer that one tiny int from one program to the other?
Thanks in advance.
janine
For UWP applications you should use Clipboard class.
OpenClipboard is an old Win32 API that is only available to desktop applications as mentioned at corresponding MSDN page:
Minimum supported client Windows 2000 Professional [desktop apps only]
I have an (non-MFC) Windows application written in C++ (Visual Studio 2013) running on a small device running Windows Compact 2013.
The device has two storage volumes (internal flash memory and SD Card)
If I connect the device to a Windows PC via USB cable, the volumes are mounted and I can see them as two separate drives inside Windows Explorer. I am then able to change the label of each volume inside Explorer (right click on the drive -> Properties -> type in a new label)
I would like to have the ability to label the volumes from my application running on the device.
I have tried various Compact 2013 API calls without success (obviously the Compact API is far more restrictive than the full Win32 API).
I have even tried to call a script file to call the LABEL command. Also without success.
Can anyone offer me any advice about how to accomplish this? Any help would be much appreciated
Many thanks
In the end, the solution was surprisingly simple. I added an autorun.inf file to the root folder of the device with the following content
[autorun]
label=My Label
This had exactly the effect that I was looking to achieve.
I have made a project using SkeletonBasics-D2D of Kinect XBOX 360 in C++ on gesture recognition. I have also used OpenCV in this project. Now I want to make GUI of this project for better representation. But I am not able to do this using Windows Form Application..I am new to Visual Studio 2010 and kinect.Kindly help me out of this problem.
Is there a reason you're not using WPF instead of a Windows Form Application? The Kinect for Microsoft SDK samples use WPFs due to its stronger capabilities with displaying/dealing with visual elements. The learning curve isn't that huge to go from Windows Form to WPF imo, and there are plenty of blogs that can help you get started or answer most questions you'll have to start off:
Here's a list of WPF blogs: http://blogs.msdn.com/b/jaimer/archive/2009/03/12/wpf-bloggers.aspx
My favorite is the 2000 things blog.
In WPF Kinect applications, there's typically an Image element in the .XAML side whose source is set to a WriteableBitmap property in the back-end code. On each Color Stream ready event (or any stream for that matter) you can write the new set of pixels to the WriteableBitmap and the WPF image element is instantly updated. I haven't tried using Windows Forms but I think it's a lot more work for a less-clean product.
shown in image and let me know which option to create window phone app visual c++
You can't do that. There is no adequate option to create regular Windows Phone app only in c++. If you'll create Direct3D app with XAML - all interface will be in c# with Direct 3D view in Direct 3D with c++. If you'll create Direct 3D native only - you'll need to create all interface by hands. There are a lot documentation pages.
Native code on Windows Phone 8,
C++ support from Windows Phone 8,
And right here, at SO -> Is it possible to program for Windows Phone 7 in standard C++ only? (with answer about Windows Phone 8)
There is no pure C++ template for Windows Phone, only project templates for game development are supported. This is due to the XAML architecture differences between Windows 8 and Windows Phone 8. While the former uses WinRT controls for XAML thus enabling projections for C++, Windows Phone 8 XAML is still the Silverlight runtime which is not projected into C++ and is based on CLR.
I need to retrieve the physical sector size of a hard disk to determine if the hard disk is of advanced format or not in Windows XP.
I tried to use STORAGE_ACCESS_ALIGNMENT_DESCRIPTOR, but it is not compatible in Windows XP. Any method I use would return 512 instead of 4096, which includes WMI where the only value returned is 512.
I have been coding in C++ and I would be very thankful if one can point me to a method which would help me find the actual physical sector size.
According to Microsoft's MSDN article:
Windows XP, Windows Server 2003, and Windows Server 2003 R2 do not
support 512e or 4Kn media. While the system may boot up and be able to
operate minimally, there may be unknown scenarios of functionality
issues, data loss, or sub-optimal performance. Thus, Microsoft
strongly cautions against using 512e media with Windows XP or other
products based on the Windows XP codebase (such as Windows Home Server
1.0, Windows Server 2003, Windows Server 2003 R2, Windows XP 64-bit Edition, Windows XP Embedded, Windows Small Business Server 2003, and
Windows Small Business Server 2003 R2).
Under Windows XP, you will not be able to get a true physical sector size because the OS itself assumes that it is 512 bytes.