I am working on some strange issue with my delphi application.
The scenario is as follows:
If microsoft Lync is running on my machine and if I want to launch my application, it does not getting displayed but the process was started for my application.
and when I close the lync, immediately my application gets visible.
Below are some points which you may need:
My application does not have any link with Microsoft Lync.
Application process is running when I close the lync
Form.Show() is the last statement called from my code.
This issue is not replicated on every machine.
I am not sure why this is happening.
Can anyone help me on this?
Any help or suggestion will be useful for me.
Thanks in advance.
Finally,
After a long checking of the code I came to know that this problem is due to the setting desktop as a parent window somewhere in the code.
Refer this link for SetParent().
When this problem has been discussed with the microsoft I came to know that the Lync is having some issue with some application when we call SetParent(Handle, 0) this will go for a long wait state.
Solution:
What I did is as the SetParentfunction call was important in my code I assign the SetParent property of the form to my application handle so this solves my problem.
The above step is done because in spy++ I found that every delphi application as 2 instances 1 is for TApplication and another is for MainFrom i.e. TForm of the same application.
Related
I am facing the below issue while working on BluePrism, the issue relates to spying elements from a windows application called "Cashier", the application is written in VB, I provided the .exe file for it and the application launched properly, however, I can't properly spy the individual rows in the table shown in the attached picture. I can only spy the box as a whole, and no information is retrieved.
possible the application spawns the elements in a new process? perhaps check the task manager once and make sure another process hasn't spawned to show the results in?
I am working with MS Support on a case. We've found that when running an install/update on our application, that it doesn't work as expected on Windows 10.
A window inside our application is returning an error when the Windows Restart Manager sends a WM_QUERYENDSESSION to it. This results in an aborted shutdown on our app during the install.
With the help of Microsoft Support we've determined that it is the "URL Moniker Notification Window". I also know which thread owns the window. But I don't see anything in that code that rings a bell for me.
Where does this window come from? How did I get this in my process?
No answer was ever found. Ultimately, replacement of our installer (w/ WIX) made the world a better place.
I have written file picker code in my project. When i run the project in my windows phone by clicking on device button in visual studio, the app runs fine(I mean it opens pictures library and i can select a photo and preview it).
But when I disconnect my usb and then open the app in the phone and when i open pictures library on click of a button , the pictures library opens briefly and then the app crashes immediately(My app closes).
Can anyone please help me with this??
As written in the blog post , the AndContinue method run in a different process and to do so, the current running app goes into the background or even gets closed sometimes, that is what you are experiencing in your app as far i can tell but not sure why different things happening during debug & deploy.
There must be a callback inside app.xaml.cs specifically to handle the condition when calling application(which was sent into background) comes in foreground, read this blog post carefully & you'll understand as what you need to change in your code :
using-the-andcontinue-methods-in-windows-phone
http://blogs.msdn.com/b/wsdevsol/archive/2014/05/08/using-the-andcontinue-methods-in-windows-phone-silverlight-8-1-apps.aspx
I just dealt with this issue and one of the reasons why there are differences between debug and deploy is because of the suspending event.
During debug, the application does not actually get suspended until you manually do it through Lifecycle Events. This means that when you pick a file on debug and the app is put to the background to load the file picker, it is not actually suspended, while when the app is deployed, it actually gets suspended.
Look into your app_resuming method and OnSuspending methods in your app.xaml that may be causing errors not occurring during debug.
My wp7 app crashes when I come back from a task such as Map, Call or Web Browser. Infact, if i lock my phone and resume it again, still it crashes. Please tell me what could be the problem and how can I remove it?
There is a problem with you code.
Remove the application off the phone by starting a new emulator instance.
Open App.xaml.cs
Put a breakpoint in the method RootFrame_NavigationFailed and Application_UnhandledException
Now use the CallStack to find the root of the issue.
With no code posted (and in your case it could be ANYTHING in the project) you will be the best person to resolve your issue. If you can post a small reproduction on here we can take a look.
In application exit methods you probably should restore the data you dealt with last time before you quited
I have a particular piece of software that i wish to load on windows startup. Under normal circumstances i would simply place a shortcut in the startup folder or an entry in the run key in the registry.
Unfortunately and for an unknown reason this application throws a win32 execption whenever that is done - and i am assuming it is because an element of windows has not been loaded that is vital to this application.
Once windows has actually loaded i can double click on the icon and it runs fine. So my question is - is there a programmatic solution to this? I have already tried a console app launcher that sleeps for n seconds and then launches but all that seems to do is delay the startup of windows.
Does anyone have any creative solutions? I am open to anything from a windows service to c#, vb, batch files.. etc
Thx
Can you run it as a service, or write a shell service which will attempt to start it up? That way you will have built in support for response on failure and delay time before trying again.
Have a look at AUTOEXEC.BAT. But be careful!!