Planning the 2.0.0

[zero-plusplus]

Currently, I am rewriting the source code from scratch to improve future extensibility and maintainability.

The work can be viewed on the v2.0.0-develop branch.

---

I realized that marking something once doesn't make sense because I may end up reworking it later for refactoring or fixing it. Therefore, I'm going to treat it as a list of things I need to do, not as a progress indicator.

Existing features

• Debug configurations
  • Verification / Normalisation
  • Support for new attributes
• Meta Variable
  • Responding to changes in specifications
• Data inspection
  • Context menu
• Call stack
• Watch expression
  • Update evaluation process
  • Loaded scripts
  • Conditional breakpoint
  • Update evaluation process
• Hit conditional breakpoint
• Log point
• Debug console
• IntelliSense in debugging
• Perftips
• Breakpoint directive
• Output directive

• ClearConsole directive

Add

• [ ] #31
• [ ] #224
• [ ] #241
• [ ] #257
• [ ] #264
• [ ] #266
• [ ] #271
• [ ] #272
• [ ] #286

Change

• [ ] #60
• [ ] #116
• [ ] #225
• [ ] #238
• [ ] #239
• [ ] #240
• [ ] #244
• [ ] #261
• [ ] #269
• [ ] #275
• [ ] #282
• [ ] #288
• [ ] #293
• [ ] #306
• [ ] #307
• [ ] #309
• [ ] #312
• [ ] #320
• [ ] #322

Fix

• [ ] #207
• [ ] #212
• [ ] #215
• [ ] #220
• [ ] #229
• [ ] #232
• [ ] #234
• [ ] #236
• [ ] #245
• [ ] #254
• [ ] #255
• [ ] #256
• [ ] #262
• [ ] #273
• [ ] #283
• [ ] #285
• [ ] #291
• [ ] #292
• [ ] #301
• [ ] #302
• [ ] #311
• [ ] #321

---

Remove

• [ ] #213
• [ ] #248
• [ ] #263

---

Task

• [ ] #289
• [ ] #294
• [ ] Add a note to the wiki on how to debug scripts that use administrative privileges
• [ ] Update Evaluator to match metavariable specification changes. e.g. GetMetVar("variableCategories").Global
• [ ] If an error occurs in a library available in the expression, it raises an error rather than returning an empty character and displays this information in the console

Confirmation

• [ ] #302

• [ ] #317

Backlog

• 253

• 313

• 314

---

Remaining work to release

• [ ] Test
• [ ] Check security patches

[mark-wiemer]

Hi, I worked with Stef Levesque to discontinue slevesque.vscode-autohotkey, see https://github.com/stef-levesque/vscode-autohotkey/issues/32. My extension, AutoHotkey Plus Plus, shouldn't cause conflicts with the debugger as it's hardcoded to use your extension if it exists.

My goal is to have one extension (or extension pack) that AHK coders can use to write both AHK v1 and AHK v2 scripts with full language support--good IntelliSense, syntax highlighting, formatting, and debug support.

I'm hoping we can work together to discover the best way to support AHK coders moving forward, I'd hate for us to both do the same thing. Please let me know if there are any conflicts between AutoHotkey Plus Plus and your extension, and I'll work to remove them.

[zero-plusplus]

Thanks for the explanation.

You and I have different goals. My initial goal was to assist in the creation of my own library. Therefore, I want the extension to fulfill 100% of my requirements. This can only be achieved by my own creation.

And unfortunately we will not be able to cooperate. I would also not collaborate, because the multi-person development would be a barrier to incorporating my own ideas.

We will create similar extensions, but they will each have their own good and bad points. They may lead to better subsequent extensions.

That would be preferable to me.

---

I will report back to you when there is a possible conflict😄