Hi,

I have set up a Trigger on 'Window Created':
- Frequency: Always
- Stop processing triggers if this one matches: not checked
- Process Filename: C:\T32\bin\windows64\t32mppc.exe
- Process Command Line Parameters: not checked
- Window Text: "TRACE32 PowerView for PowerPC 0 [Power Debug USB 3 @ ]"
- Window Class: "T32"
- Monitor Profile: "Lab 3 Monitors"
- Actions: Wait 2000ms, then Move Window to Specific Size and Location.

Sometimes this trigger simply does not work. When I open DF settings, go to Triggers, double click on the trigger, then click OK without changing anything, it suddenly works again.

Attached a log. Events:
~1:32PM: Opened the program TRACE32, which should trigger => Nothing happens
Open DF settings, go to Triggers, double click on the trigger, then click OK without changing anything, it suddenly works again.
~1:34PM: Opened the program TRACE32, which should trigger => Trigger works and resizes

The system is windows 10, 64 bit.
It would be good to get this working constantly. I have the feeling that after logging in and working for some time (with multiple changes of monitor profiles, i.e. walking form one desk to another) DF seems to loose track of events.

Regards,
Christian

That window title never changes and neither does the window class. DF has this "sniper" icon which I can drag over a window to get title or class. If I drag it over a window which has failed to trigger, I nevertheless get the same title and class which is already entered for that trigger.

I need at least one of these conditions, because the process starts lots of other windows while running and DF tries to resize them, if I not told to watch for a window class.
I'll remove one of these conditions and see what happens.

I have the feeling that there's still a clash between my Windows 10 setup and DF. I have some scripted functions assigned to hotkeys, and usually the execution of these functions triggers a small notifiction window. Sometimes it doesn't.
And I have the feeling that this lack of responsiveness has something to do with time of day. In the morning after logging in everything runs smooth, but later that day it gets tedious. I am moving between different docking stations a lot without logging out. Maybe this is the issue?

CU,
Christian

I'll do that, but first for some I'll try the setting with only one of the two trigger conditions.
It will take some time to see the effect during daily work.

So by now I'm running DF 9.2.2.

The problem is still there.

Overall I have the impression that DF is running smoother since 9.2. Since my upgrade to Win 10 there was lots of lag and stuttering, starting with the "Wave-Bar" animation when opening a DF window.

CU,
Christian

Taking out Window Text makes a difference. The problem is that the software has some other windows with the same Window class which I don't want to have changed.
But I think I have a solution with the new delay feature.

The software checks for an external interface on the USB when it starts. If that interface is not there, it shows an error message. Then it closes when I acknowledge the error. I made some tests:
If I disconnect that interface and have match for Window Text deactivated, then DF resizes the main window, even with the error message shown. If I have match for Window Text activated, DF does not resize.
And that although in both cases the title text on the screen is the same. But it seems that DF only gets the correct text form the software, after successful check of the interface.

My theory is that sometimes my laptop is very slow and the interface check delayed, even with connected interface. Then DF gets not the correct Window Text reported.
So the delay feature should be able to fix this. Right now I'm trying 200ms. Should I see "misses", I'll increase the value.

Regards,
Christian