https://1drv.ms/u/s!AkVRV9eGJ20rgTu13uTcNkhp0eZb?e=lwMe70
That links takes you to my OneDrive where you can download my Visual Studio 2022 solution and project (it is a .7z file of 17.7KB), it only has code to display a win32 window and little more. I also included an image that tells you my DirectX specs that the DirectX Diagnostic Tool reports. The image is the following image:
The problem is what the title says, I would like you to see if you can compile it without problems, I am afraid that it may be failing because I can't use Direct3D 11.1 (is Direct3D 11.1 a requirement? I can't find information about it), but then I tried creating the D3D device with the D3D11_CREATE_DEVICE_PREVENT_ALTERING_LAYER_SETTINGS_FROM_REGISTRY creation flag (https://learn.microsoft.com/en-us/windows/win32/api/d3d11/ne-d3d11-d3d11_create_device_flag) just to test if I can use Direct3D 11.1 (because that flag is not supported until Direct3D 11.1) and the creation succeeded... so I don't know anymore...
When you program with DirectX make sure you always enable the "debug layer" in dev and check the output in Visual Studio's "Output" window (or other debugger output).
Check these links: Using the debug layer to debug apps and Direct3D SDK Debug Layer Tricks for more on this as the way it can be installed has changed over DirectX version and years...
This will show you why it fails:
Alpha blended swapchains must be created with
CreateSwapChainForComposition, or CreateSwapChainForCoreWindow with
the DXGI_SWAP_CHAIN_FLAG_FOREGROUND_LAYER flag.
I'm coding on xamarin to create an Android-form test application in vs2017.
The coding isn't the problem its rather the environment.
So far the biggest problem has been getting it all to work in vs2017. I managed to get it mostly working, with minor (yellow) errors left.
Now the device xaml preview works !!
The Visual studio / (or should I say intel Haxm) emulator works !!
And I can use the live player as well !!.
My program can be seen on all of above (also on my mobile).
So now that it finally all works (fixing the environment took quite a while).
I got carefully to update my environment and xamrin, and I wonder I have installed Android build tools 26 and 25. (As I want my code to run on my older 4.4.2 version of android phone. Would it be fine to install android build tools 27.0.3 as well??.
Or will adding another sdk-build-tools cause havoc (dependency troubles).
I'm not sure if those build tools are independent from the rest of xamarin / .net core
build tools used, should be latest only,sdk build tools are independent, if u r talking about sdk tools then u can add as many as u want like if u want your emulator to be run on that sdk version then u need to download or else downloading multiple sdks will affects only to size nothing else
I've got the printer driver, P-touch Editor, b-PAC 3.1 and client tools, all 64-bit, downloaded from the Brother website and installed on my 64-bit Windows 7 laptop. The P-touch Editor works/prints fine.
However, b-PAC failed, and none of the samples worked. I debugged the code:
bool b = doc.PrintOut(1, bpac.PrintOptionConstants.bpoDefault);
where b is false. What could be wrong?
I was hitting the same problem, everything appears to work right up to the point where I called "PrintOut", which fails with error 11, "The currently specified printer is not supported".
It turns out the problem I had was with the driver. I had installed the printer driver from the CDROM that came with the label printer. Windows 7 also comes with an "in-box" driver for the printer and in fact this is the one you should install (it's marked with an "LE" at the end).
To fix the problem, all you need to do is go to the "Devices and Printers" dialog, select the printer, right click on it and select "Printer properties", select the "Advanced" tab and click "New Driver". Find the printer in the list that matches yours but with an "LE" at the end and click OK.
Printing is possible with either of the drivers using the P-Touch editor. Odd thing is, "LE" appears to stand for "Light Edition", but the "Heavy" version doesn't work!... strange.
On my Windows 10 x64 machine, I've had a similar issue using Ruby to print through the bPAC SDK (using win32ole). My code worked on another machine, but not mine.
After fighting with this for a long time, I figured out that all was fine and dandy when using the 32 bit version of the bPAC SDK (and Ruby). Don't know exactly what went wrong here, but it might be that the 64bit SDK is just broken.
I had a similar problem, so I added this after the printOut to see which code I was getting.
string sError = doc.ErrorCode
It returned Error 11, which corresponds to "Device is not supported", but the device was a QL-570 which IS supported.
To get it working, I used the following steps:
Side-install the 32bits sdk.
Open your 64bit sample.
Change target configuration platform from "any cpu" to "x86"
Compile
See also: Label printing development using b-pac SDK in a C# application
The important thing is the application that you uses.
If your app is a 32bitapp (inclusive excel) you need the bPAC SDK for 32bit even when they are running on 64-bit Windows OS.
Some printers only support 32-bit b-PAC SDK ver.
(even if you use windows 10 64-bit with Excel 64-bit)
please check:
https://support.brother.com/g/s/es/dev/en/bpac/environment/index.html
I had the same problem (printOut gave me the error code 11).
The error appeared after switching from the printer PT-9800 to PT-P950.
Trying 32 and 64bit did not work for me.
What fixed it was uninstalling the driver of the PT-9800. I found a hint in the b-PAC 3.4 SDK Help in the section Troubleshooting: "if the old label printer will no longer be used, we recommend deleting the printer driver."
I can't get Emgu CV to work with the cameras on the new Atom based Windows 8 x86 tablets. These are not the ARM based tablets running Windows 8 RT these are running the full blown Windows 8 Pro x86 on x86 Atom CPUs. I've tried working code on a release version of the Samsung XE500T1C (Ativ?) and on a pre-release version of the HP ElitePad 900.
Emgu CV tells me: "Error: Unable to create capture from camera 0". The problem is probably related to the fact that the new Atom chipset is handling some of the camera functions. I've attached a screenshot of the device manager with the offending cameras highlighted.
Under Imaging devices we have:
Intel(R) Imaging Signal Processor 2300
Under System devices we have:
Camera Sensor OV2720
Camera Sensor OV8830
Flash LM3554
I've searched the Internets high and low and can't find anything useful. I've contacted HP and they're contacting their engineering. I tried Intel and the best I got was this: http://software.intel.com/en-us/articles/sample-windows-store-app-for-camera-picture-taking which is actually for the Windows Store apps. Although it does work.
Does anyone have any ideas? Needless to say I'm in a bind. One other thing Emgu CV is working fine on my Samsung Slate Series 7 that is running Windows 8 Pro. It also runs fine in a 32-bit Windows 8 Pro VM. It just appears to be these new ones with the new Atoms with the Intel Imaging Signal Processor 2300.
Thanks everyone!
Hal
I rolled Emgu back to 2.1.1 from December of 2010. This appears to work fine with the new Intel Clover Trail Atoms.
FYI: I also tried the 2.4.9 Alpha dated 2013-01-14, but that would not work.
I understand this is an old technology, but I have been using it forever and own the software so I can't really change. I just installed Fireworks 6.0 on a Windows 7 box and even thought I can use the keyboard to get to my tools I can't actually CLICK any of my tools. It is the strangest thing I have ever seen. Could this be a Windows 7 issue because I've installed this product countless times on Windows XP machines and I can't ever remember this happening....HELP!
The issue with using Fireworks 6 ended up being even more bizarre than I originally thought. On my new laptop running Windows 7 I can not click to anything in my toolbox HOWEVER when I put Fireworks on my second monitor I can click everything in my toolbox. I found this out quite by accident.
I had an issue with old fireworks on windows 7 where it would not save preferences, one of the fixes was to enable compatibility mode and set it to run as administrator, you can do this by right clicking on the fireworks icon.
Hope that helps this problem too.