pseakins Posted March 3, 2016 Share Posted March 3, 2016 Sure, it works without the comments. The actual code I am debugging is commented. Phil Seakins Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 3, 2016 Share Posted March 3, 2016 2 hours ago, asdf8 said: How can I reproduce this error? Sorry it is not a problem. I'm edit my post above. It is only in case when comment block is above of #include <DBUG.au3>. 2 hours ago, asdf8 said: This is a special case of another problem. There also includes debugging scripts using PE-resources from the compiled applications, debugging script running as a service, debug interprocess communication scripts, etc. All this can be solved by debugging compiled script. The next version will have the opportunity to add to the source code debugger, which can then compile and debug in real conditions of use. You are right. May be you can use the same method as I'm - stdout console. You opinion on 3) ? Link to comment Share on other sites More sharing options...
asdf8 Posted March 3, 2016 Share Posted March 3, 2016 2 hours ago, pseakins said: This example fails This is a serious bug in the new version it will be fixed. On 02.03.2016 at 5:03 PM, valdemar1977 said: Very low on huge arrays. Not possible to select array columns range. Well, if the array has more than 20 columns or more than 100 rows it will request to limit the output. On 02.03.2016 at 5:03 PM, valdemar1977 said: May be in future change all vars on $_DBUG_varname for excluding any future interfere with script vars? Ok 4 hours ago, valdemar1977 said: By the way @asdf8 why by default you put @Error in conditional breakpoints and @Error @Extended in commands? May be they need to be clear on first start? Ok 2 hours ago, valdemar1977 said: May be you can use the same method as I'm - stdout console. I can return to the console, but do not see how it can help in other cases (except for the debug console applications) Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 4, 2016 Share Posted March 4, 2016 16 hours ago, asdf8 said: Well, if the array has more than 20 columns or more than 100 rows it will request to limit the output. Hi @asdf8 Yes, it is right, but you limit array only by rows not by columns. For example if my array has 300 columns and I need to see values its not help me in this case. Also I'm found strange graphic issue with ArrayView window. Its look like a grey space at the right of spreadsheet. It is only for arrays with a number of columns more then 11 . Please run attached script and try to visualize $ArrayHuge. array.au3 Also I'm find that main _DBUG window is freeze on lot of time on huge (2000:2000 elements) arrays when I'm press pause. May be it is because you try to show a lot of values in main _DBUG window? Link to comment Share on other sites More sharing options...
asdf8 Posted March 4, 2016 Share Posted March 4, 2016 1 hour ago, valdemar1977 said: Yes, it is right, but you limit array only by rows not by columns. This possibility implies a new version. Let me, in the near future, I will lay out a new version. Then, all together, we will find new bugs and verify old. Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 4, 2016 Share Posted March 4, 2016 2 hours ago, asdf8 said: all together, we will find new bugs and verify old I'm ready friend!!! Link to comment Share on other sites More sharing options...
asdf8 Posted March 5, 2016 Share Posted March 5, 2016 New version: Added the ability to create scripts with a debugger to compile. Returned to debug with OEM-console. Changed interface. Fixed detected the errors. Others improvements and additions. Dbug_2016.03.05.zip valdemar1977 1 Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 5, 2016 Share Posted March 5, 2016 1 hour ago, asdf8 said: New version: Added the ability to create scripts with a debugger to compile. Returned to debug with OEM-console. Changed interface. Fixed detected the errors. Others improvements and additions. Dbug_2016.03.05.zip Great update!!! Will test it. Link to comment Share on other sites More sharing options...
pseakins Posted March 5, 2016 Share Posted March 5, 2016 2 hours ago, asdf8 said: New version: Dbug_2016.03.05.zip Good idea to have separate .INI for each script under test! When hitting escape after debug session finished, keyboard/mouse focus does not always return to Scite editor. Ie., load Test_1.au3, hit F5, F8, F8, F5, Escape - windows has no focus. Phil Seakins Link to comment Share on other sites More sharing options...
pseakins Posted March 5, 2016 Share Posted March 5, 2016 (edited) 5 hours ago, asdf8 said: New version: Dbug_2016.03.05.zip I want to change line 361 so that JumpTo = true is the default but lines 360 - 367 are unreachable code. Never mind. I found 388 needed to be changed too. Edited March 5, 2016 by pseakins Struck out original comment. Phil Seakins Link to comment Share on other sites More sharing options...
pseakins Posted March 5, 2016 Share Posted March 5, 2016 On 3/3/2016 at 2:12 AM, asdf8 said: This is a serious bug in the new version it will be fixed. Thanks for fixing the continuation line issue. Great work! Phil Seakins Link to comment Share on other sites More sharing options...
asdf8 Posted March 6, 2016 Share Posted March 6, 2016 11 hours ago, pseakins said: When hitting escape after debug session finished, keyboard/mouse focus does not always return to Scite editor. There is a error. I thought it was because I use heavily modified editor. 11 hours ago, pseakins said: I found 388 needed to be changed too. It will be necessary to make a debugger initialization audit. By the way, can somebody confirm or deny my assumption - TAB-control in the AutoIt, can often lead to the freezing of the application window? Link to comment Share on other sites More sharing options...
gcriaco Posted March 7, 2016 Share Posted March 7, 2016 (edited) It world be wonderful if during a debug session the next debug statement in the scite source code would be always visibile - I mean that scite should automatically scroll text. It would be very useful if coders need to debug code inside functions. Not sure if it's possibile. Btw, many thanks and best regards Peppe P.s.: IMHO this debugger should be included in the sciteforautoit package Edited March 8, 2016 by gcriaco Link to comment Share on other sites More sharing options...
jaberwacky Posted March 8, 2016 Share Posted March 8, 2016 (edited) Nevermind Edited March 8, 2016 by jaberwacky I'm an idiot. Helpful Posts and Websites: AutoIt3 Variables and Function Parameters MHz | AutoIt Wiki | Using the GUIToolTip UDF BrewManNH | Can't find what you're looking for on the Forum? Link to comment Share on other sites More sharing options...
asdf8 Posted March 8, 2016 Share Posted March 8, 2016 19 hours ago, gcriaco said: during a debug session the next debug statement in the scite source code would be always visibile - I mean that scite should automatically scroll text. Sorry, I do not understand what is meant: that the default "Jump to Line with Breakpoint" button is not pressed, or that when pressed, there is no auto-scroll text in SciTe, or is it something else? 19 hours ago, gcriaco said: It would be very useful if coders need to debug code inside functions. Not sure if it's possibile. The debugger provides such an opportunity. Link to comment Share on other sites More sharing options...
gcriaco Posted March 8, 2016 Share Posted March 8, 2016 You're right. I didn't see the option button "Jump to line with Breakpoint". Sorry for mistake and thanks for support and for sharing your code with the AutoIt community. Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 9, 2016 Share Posted March 9, 2016 (edited) On 05.03.2016 at 9:02 PM, asdf8 said: New version: Added the ability to create scripts with a debugger to compile. Returned to debug with OEM-console. Changed interface. Fixed detected the errors. Others improvements and additions. Dbug_2016.03.05.zip Hi @asdf8. Small bug in lines 395-397. For $val = 1 To 25 ;enable buttons ControlEnable($frmDBUG, "", "[CLASS:Button;INSTANCE:" & $val & "]") Next You set $val var as counter of button id and the use this counter on lines 406-407 GUICtrlSetTip($DBGListView, "Display expressions" & $val) GUICtrlSetTip($DBGbtnClearList, "Clear expressions list" & $val & @CRLF & @CRLF & "To disable updates expressions list," & @CRLF & 'click the button while holding down "Ctrl"') As result wrong button and list tip in some cases. Edited March 9, 2016 by valdemar1977 Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 9, 2016 Share Posted March 9, 2016 (edited) On 06.03.2016 at 11:59 AM, asdf8 said: TAB-control in the AutoIt, can often lead to the freezing of the application window Well, in some cases I'm has a problems with redrawing TAB area (in Windows 8.1 x64) when starting in x64-bit mode... Edited March 9, 2016 by valdemar1977 Link to comment Share on other sites More sharing options...
valdemar1977 Posted March 9, 2016 Share Posted March 9, 2016 On 07.03.2016 at 11:56 PM, gcriaco said: IMHO this debugger should be included in the sciteforautoit package In fact Autoit need a full featured IDE including source editor, debugger, GUI builder, project management and so on (as an example @ISI360 Autoit Studio). Link to comment Share on other sites More sharing options...
ISI360 Posted March 9, 2016 Share Posted March 9, 2016 Just for the records: This Debugger is already included in the ISN AutoIt Studio. (Tools -> Debugging -> Advanced Debugging with DBUG) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now