![]() |
Forum Index : Microcontroller and PC projects : MMEdit mark lines as DEBUG inop.
Author | Message | ||||
Paul_L Guru ![]() Joined: 03/03/2016 Location: United StatesPosts: 769 |
Using MMEdit V3.7.0 OS Ver 10 when I highlight a bunch of lines and select Advanced > Mark selected lines as DEBUG nothing visible seems to happen to the code. Thinking that the marking was invisible I then selected Advanced > Mark DEBUG lines as comment and again nothing visible happened to the code. Does anybody have any ideas about what I'm doing wrong? Paul in NY |
||||
disco4now![]() Guru ![]() Joined: 18/12/2014 Location: AustraliaPosts: 1003 |
Paul, Worked fine for me first go then stopped after looking at version no. Minimised all windows and version box was open, closed this and worked again. Playing around a save dialogue was open in background which also stopped it. Looks like you can have a background form hidden which stops it working if you dont see/close it. Regards Gerry Latest F4 Latest H7 FotS |
||||
TassyJim![]() Guru ![]() Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
The 'about' window is a MODAL message box which is supposed to stop you from doing anything in the parent box while it is open. I will change it to 'always stay on top' which should help. The edit control does do some strange things at time which makes control of the parent window difficult at times. This is why you often need to click twice when returning to the edit window. Bloody annoying! Paul, If Gerry's observation does not apply to you, I need more information. Jim VK7JH MMedit |
||||
TassyJim![]() Guru ![]() Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
See if this makes things better. As usual, replace the TKN file in your program folder with the one in the ZIP 2018-08-01_165330_MMedit.zip Jim VK7JH MMedit |
||||
Paul_L Guru ![]() Joined: 03/03/2016 Location: United StatesPosts: 769 |
Hi Jim, MMedit is a little flaky sometimes. It started adding the debug mark as a visible "'DEBUG" appended to the end of the line. You have to carefully select the lines before requesting the debug mark. If I then reselect the lines each time I can comment out the debug lines, remove the comment, and remove the debug mark. I moved in the MMedit.tkn file dated 8/1/18 you provided after renaming the older one to oldMMedit.tkn 4/9/17. The new file did not change the behavior at all. I only had the main edit window open when trying to do this. As I said above I don't really write in MMedit, I use notepad++ with multiple files open in different windows. I write and test individual subs and funcs in their own window then move the entire sub or func into my main code when I'm satisfied that it works. In notepad++ I mark my debug lines with a "'<dbf>" at the end. Now that I have finally seen your debug mark, "'debug", at the end I can change my "'<dbf>" to yours in notepad++ and MMedit will be able to manage them. Your >P>O format and >P>V variable usage report functions work very well and are invaluable. I use them all the time. There is one nagging incompatibility. Notepad++ has the ability to display folded code. Alt+0 will display only those lines with no leading spaces. Your format routine adds two leading spaces to all lines except for labels, Sub definitions, End Sub lines, Function definitions, and End Function lines. When I hit np++ Alt+0 I see only all the lines which are labels, sub declarations, function declaration, end sub, and end function. All the end sub and end function lines are needlessly annoying, so I do a bulk replace of "end sub" with "__end sub" and "end function" with "__end function" which then causes np++ to just display the labels and declaration lines. All in all the two editors work very well together. Thanks for your good work. Paul in NY |
||||
![]() |
![]() |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |