I am implementing a CD/DVD burning tool by using IMAPI (Image Mastering API by Microsoft). I need to put a ProgressBar into the main screen to indicate user about the progress of writting process.
I am using Microsoft Visual FoxPRo 9.0 SP 2 for my development.
Can anyone can tell me how can I collect the statistics to set the values of the Progress Bar...??
Please Help
Thanks in Advance
This is really an IMAPI question surely?
This similar query would seem to indicate that you need to handle IDiscMasterProgressEvents progress events from IMAPI, and possibly on a separate thread. So I'm not sure how feasible that would be with Visual FoxPro.
You might find it easier to do this in .NET and then leverage that from the VFP side.
Related
I am developing a small tool that can detecting which folders are being opened in windows explorer and bring it to front if a specific address has been opened.
I can use both C# and C++ and finally pick C# as it is easier than C++ to accomplish the same target. Then I googled the internet and knowing COM object SHDocVw.ShellWindows can help collect all windows being opened. Then I start looking for Microsoft document to see if any functions can help to achieve my other requirements. However, when I search shell related documents: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ff521731(v=vs.85) I am warned that "We're no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported." Moreover, some documents even say these techs will be deprecated in Win11 (See the following screenshot)
I am wondering what the status of these Shell related technical. If these are being deprecated. What's the alternative solution? I don't want my tool stop working when start using new Windows. Meanwhile, I am confusing in the study routine of learning Windows desktop technical. Looks like so many technical to achieve the same targets. Is there anyone can give me some road maps?
Last thing, it's really frustrating to search COM object documents at Microsoft sites. Is this tech going down?
Microsoft has been trying to kill win32/desktop applications since Windows 8. That parts of the documentation is labeled as "legacy" is not something I would worry too much about. Some of the shell functions have been marked as deprecated for 20 years but still work fine today and too many applications rely on them for Microsoft to successfully remove them.
The Internet Explorer warning is different and IE might actually go away but that does not affect IShellWindows which is also used by Explorer.exe and 3rd-party applications. Its implementation lives in a shell DLL and not in IE.
We are working on a project that involves the conversion of old DOS based screen panels to Windows based graphical user interface using GUI Screen IO.
We got in touch with the company recently to purchase the software but company is apparently in transition of selling and have discontinued the business of providing the licensed S/W. So, we are unable to get a licensed copy of this GUI ScreenIO s/w which would impact our project.
Q -- Has anyone ever heard of another presentation layer s/w that is very similar to GUI ScreenIO and can work with native Cobol? Please let us know.
Thanks,
Kishan
Your info about the discontinuation of Gui ScreenIO comes a bit as a surprise to me.
I am a GuiScreenIO user myself and have heard nothing from the vendor about an end-of-life strategy, what so ever, and was billed for support just a few months ago!
If what you state is true (and I have no reason to doubt your writing), I will have to look for an alternative myself as well.
There is an alternative product called SP2 (Flexus) that has an approach comparable to GuiScreenIO. Since you are at the beginning of the character-based-to-windows-transition you might want to take a peek at it! ;)
Feel free to ask if you need more info about transitioning character based cobol applications to Windows.
Kind regards,
Paul
Application Insights has a great feature that can open an execption in Visual Studio and then debug with the current state of all the variables and objects.
I have been looking around for a open source alternative that can do the same, but I have not found anything similar. What I want to achive is quite simple. I want to dump all the state of my objects/variables when an exception occours, save it somewhere and then later on be able to load it into Visual Studio.
Any ideas how to achieve this?
Application Insights appears to be an Application Performance Monitoring tool.
These generally seem to be language/platform specific, but the best known open source alternative I could find is called insepctIT, which is for the Java ecosystem.
It appears that you can cobble together multiple tools to get the same job done in other ecosystems, OpenAPM seems to have a tool that lets you compare different pieces of the overall APM workflow and put together a monitoring solution for your app.
I realize this doesn't solve the specifics of your question related to debugging in Visual Studio, but it could help others that run across this question on google.
I have VS2010 professional and Im working with a large code base that Im unfamiliar with. I want to know what code gets executed when a certain event occurs (namely, when I click a specific button). I know this could easily be done with Intellitrace, but that requires an Ultimate subscription (which is outrageously expensive). Is there any other way I can do this? Ideally without installing anything new (even if its free), but thats not a deal breaker.
You can see what .NET code is executed with Runtime Flow (developed by me, 30-day trial).
I cant get the Graphical Debugger in VS 2012 Ultimate to work, & I have no idea why.
The debugger starts ok, but when I hit the print screen button, the debugger just says its waiting for DX to draw frames. [even after I exit]
I am sure the draw refers to the Present() in the swap chain. I am calling it [thats why you see the box down there]
Is there some bug I need to be aware of?
Edit:
I think the render target might be related to OMSetRenderTargets().
I called it exactly as the SDK sample did, so I don't know what else to think.
I'm a developer on the Visual Studio graphics diagnostic tools at Microsoft. I'm fairly new on the team, and I don't believe that any previous team members were actively watching Stack Overflow, so sorry about the wait on this question.
As it's been a few months I'm guessing that you might not have the repro around anymore. So such this might be a bit hard to diagnose here and now. From what you shared it looks like the playback engine (which we use to capture and replay DirectX data while the application is running) crash while trying to collect data on your application. Sadly with the first release of our tool (In VS 2012) stability issues of this type are more common then we would like. Simply a function of how we did collection on something as complex as DirectX. However since then, particularly with Update 2, we've made some very big strides with compatibility and stability. As a first step I'd make sure that you have all the VS updates installed as Update 2 was a big upgrade for the graphics diagnostic tools in particular (Preview of 2013 as well if you have access to that).
Why don't you use PIX instead http://www.youtube.com/watch?v=-3PISvNTeB0
PIX Tutorial