Can't Detect Bt Documents Closed In 10.1 Sr3
I have an application that I am currently upgrading to use BT 10.1 SR3 Enterprise Automation from BT 9.4 SR3 EA. The following code has worked with 9.4 to detect when the user closed the BT application window but it no longer works in 10.1:
You could make use of the IsAlive property of the Engine class of the Seagull.BarTender.Print assembly.
In fact, there are some other properties such as "Documents" property and "Window" property which you could also take a look it. You will find this information on BarTender's Help (F1 key) under the "Automating BarTender > Automation with the .NET SDKs" topic.0
I have looked at all the properties that you are talking about including:
IsAlive (returns true), IsResponsive (returns true), Window.Visible (returns true). Everything that I look at makes my program think that the user is still editing the label. The only way that I can tell that the user closed the window is if I access the bEngine.Documents.FileName which generates an exception when the application window closes. This behaviour is completely different than BT 9.4 SR3 and does not make any sense. I have just upgraded to version 10.1 and I can't use this version without the SDK working properly, please forward this to your developers.
Further questions I would like to ask you:
- On which version and service pack of Windows is BT v10.1 SR3 installed?
- Was BT v9.4 SR3 running on the exact same computer and Windows version?
- Is the BarTender engine running as an application or under a service context?
Bar tender 9.4 and 10.1 were both tested on the same Windows 7 Ultimate machine, in both cases BarTender was installed locally as an application.0
I also got the same results (with 10.1) on Windows 8.1Pro.0
Could you also let me know if the BarTender engine (started by your .NET SDK program) is being started under a service context? This would imply that when you open the Windows task manager, the "bartend.exe" process is being launched under a different Windows user account than the one you're currently logged as.0
Please sign in to leave a comment.