IDE Tool "Jump to Marker"

Working on new editor enhancements?
AZJIO
Addict
Addict
Posts: 2183
Joined: Sun May 14, 2017 1:48 am

Re: IDE Tool "Jump to Marker"

Post by AZJIO »

Video
You can add settings to prevent the window from closing.
Allow the window to be resized.
User avatar
Michael Vogel
Addict
Addict
Posts: 2806
Joined: Thu Feb 09, 2006 11:27 pm
Contact:

Re: IDE Tool "Jump to Marker"

Post by Michael Vogel »

Not sure if you're happy with the modifications but...
...it is possible now to jump to a marker without closing the window (set option parameter to 1xxxxx)
...changing the window width is possible (the height is controled by the parameter values xxxx0xx or xxxx1xx)
AZJIO
Addict
Addict
Posts: 2183
Joined: Sun May 14, 2017 1:48 am

Re: IDE Tool "Jump to Marker"

Post by AZJIO »

Michael Vogel wrote: Mon Sep 01, 2025 11:19 am Not sure if you're happy with the modifications but...
I was busy with my own things. I recorded a video because I needed to record a few videos, and I also recorded your program to show it to you quickly.

Why are you still using a direct path to your source code, when people have a different path to your source code and it won't work? I've provided you with constants that will give you the correct path to your source code, and it will automatically work. This way, people can immediately check your code without having to compile or add it as a tool. If someone checks it using F5 and likes it, they'll consider adding it to their own project. However, if the code doesn't work, it will be discarded.
User avatar
Michael Vogel
Addict
Addict
Posts: 2806
Joined: Thu Feb 09, 2006 11:27 pm
Contact:

Re: IDE Tool "Jump to Marker"

Post by Michael Vogel »

Hi, thanks for your comments which are valuable for me - and you're right with your hints.

Anyhow the program is designed as a tool and works when compiled. Maybe you can call it a feature request to be integrated into the IDE (because it should be easier to get all marker positions without scanning the source code)

The debugging part (including the example file path, retrieving handles, etc.) is to play around with the source. BTW compiler path constants are not working perfectly when using a portable "installation".
Post Reply