jorgesimoes1983Regular ContributorJoined 12 years ago168 Posts55 LikesLikes received9 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: Windows 10 - Critical Error - Start Menu and Cortana aren't working There's a huge thread on this subject at Microsoft Community forums. I solved the problem by installing "Classic Shell" http://answers.microsoft.com/thread/5256ebee-2c77-4003-87be-1597ab10cb4d Another solution is using Media Creation Tool as described in the above thread. Re: Windows 10 - Critical Error - Start Menu and Cortana aren't working The problem, happened again... but I solved it like this (at least until Microsoft solves the problem...) I move the window down, so the tests can run as expected. Maybe it helps someone /** * Moves 'Critical error' window down<br> * @method erroCriticalErrorWin10() */ function erroCriticalErrorWin10(){ var propriedade = new Array("WndClass", "Name"); var valor = new Array("Shell_Dialog", 'Window("Shell_Dialog", "Critical Error", 1)'); var limite = 0; objCriticalError = Sys.Process("explorer").Find(propriedade, valor, 20, true); if(objCriticalError.Exists){ Log.Message(objCriticalError.Name); objCriticalError.Position(0,1020,0,0); } } Re: Windows 10 - Critical Error - Start Menu and Cortana aren't working Yes it's clearly a windows issue. It hasn't happened again yet, although I was wandering if anyone had any issues of this kind :) Windows 10 - Critical Error - Start Menu and Cortana aren't working I installed WIN10 yesterday, and last version of TestComplete, everything seems to work fine, although after running my Project Suite, got the error below: "Windows 10 - Critical Error - Start Menu and Cortana aren't working. We'll try to fix it the next time you sign in" Has anyone experienced this issue? Solutions? SolvedRe: Clear breakpoints by script Nice :D I see that a lot of people use high number of, "on/off variables" in their projects :) I posted a new idea because of this post, being able to set "Conditional breakpoints" condition by default, if you like it, please give kudos at the post below http://community.smartbear.com/t5/TestComplete-Feature-Requests/Clear-breakpoints-by-script/idc-p/105621#M284 Re: Clear breakpoints by script If you read post below: http://community.smartbear.com/t5/Functional-Web-Testing/Clear-breakpoints-by-script/m-p/105618#M25751 There is a solution! It would be cool if we were able to set "Conditional Breakpoints" condition by default, for instance, Condition: "enableDebugging==1" It would solve the problem :D and maybe it will be handy for other situations Re: Clear breakpoints by script Thanks! Re: Clear breakpoints by script StevenN, I had never used conditional breakpoints. It works fine, however this forces me to place the condition "enableDebugging==false" in every breakpoint condition column. Can you set the condition to appear by default? Thanks! I guess if it isn't possible the best available solution is to run the project in /SilentMode. Re: Clear breakpoints by script Yes, I understood your idea, but how do you "disable debugging" by script, without clicking the enable/disable button? :) I mean how can you access "debuggingMode" variable? For instance, you have Options Object that allows you to define some configurations, is there anything similiar to define debugging mode state (by code)? // Set the option to "Off" Options.Visualizer.CollectMode = "Off"; // Set the option to "Capture images only" Options.Visualizer.CollectMode = vcmImg; Re: Clear breakpoints by script StevenN, that is actually a good idea, but how do you disable debugging by script (without having to press the button)?