Hello, I would like to automatize my tests. For this, I am calling the Keil debugger via the dll. In my program I use debugger variables. The problem is that between 2 runs, already defined variables/breakpoints/watchpoints/functions are not cleared. I found how to remove watch and breakpoints, also functions. But, no way to remove a variable!? More generally, is there a way to be sure to have a clean environment? Delete project.uvgui.username????? (seems violent to me...)
Regards, Gelika
Have you checked what default program Windows thinks should be used when opening uvision project files? Is it the correct binary?
In my case, .uv2 is of type UV2FILE, and UV2FILE is opened by the command "C:\Keil_v5\UV4\UV4.EXE" "%1"
And as long as no explicit icon has been specified, Windows should pick up the first available icon from the UV4.EXE binary.
But if UV4.EXE points to the wrong path as a result of you having played with multiple concurrent installations, then you can get into troubles.
OK, thanks Per, Somehow the "open with" was pointing to the right executable, but re-associating it did the trick. Now I have a nice green icon showing in my taskbar. I should try another set of "find in files" to see if that issue is solved too now :-)
Rgds
So, it looks like also my (very old) issue with "find in files" is now giving the right results. For this specific issue, it's not clear what exactly did the trick, but it's solved.
Did your file association really pointed to the right binary? Did you verify the path of the binary? The only way I know how to check without looking for some utility tool is to open the scary registry and check.
But anyway - great that it works for you now :)
Hello Per, Unfortunately it's not possible anymore to know what was the previous value... So, now I've got other questions, i'll start a new thread!
Hello Per, Today I restarted (as every monday) my computer... and it appears that the icon disappeared again. It comfirms that the file association between .uvproj and uv5 was right, but the problem is that the installation is on an encrypted partition which is not mounted at startup... I mount it manually afterwards. I had issues calling the dll from C: drive (my python scripts are on the encrypted partition), that's why I put everything on the same drive...