Open dannoe opened 8 months ago
The path looks wrong on the second tab, so maybe this is why this is happening
My tests were all done in a multi project workspace.
The default "Go to definition" is using the parent folder name (as in the windows explorer) as the first path segment: app
in my case
The "AL Explorer" is opening yet another path. It is using the app-id (guid) without dashes:
And AZ AL Dev Tools is using the workspace folder name (which can be changed in the workspace file via name
)
(Also in AZ AL Dev Tools: Name is URL encoded, space to +, slash to %2F, etc.).
After some time my breakpoints are getting cluttered, looks something like this but more mixed up:
I like it that way, seeing the calling and the called procedure parallel is a boon.
I like it that way, seeing the calling and the called procedure parallel is a boon.
To switch between the caller and called position I use Alt-LeftArrow
or Alt-RightArrow
If you want to open it in a split view you can press Alt+F12
then Ctrl+Enter
My tests were all done in a multi project workspace.
The default "Go to definition" is using the parent folder name (as in the windows explorer) as the first path segment:
app
in my caseThe "AL Explorer" is opening yet another path. It is using the app-id (guid) without dashes:
And AZ AL Dev Tools is using the workspace folder name (which can be changed in the workspace file via
name
)(Also in AZ AL Dev Tools: Name is URL encoded, space to +, slash to %2F, etc.).
After some time my breakpoints are getting cluttered, looks something like this but more mixed up:
Experienced the same thing. A problem is: If you are setting a breakpoint in the duplicated file the breakpoint will not be shown in the actual .dal file. It is a bit confusing as you re-run the process you want to debug and the debugger hooks to the line of code in the "not-duplicated" file but it doesn't show the breakpoint indicator before the line (red circle) in the editor - so you are asking yourself, why the debugger hooked there.
1. Describe the bug If you navigate to code inside a dal file and try to navigate even further a new unnecessary duplicate tab is opened.
2. To Reproduce
Record "Prod. Order Line"
.TestField("Finished Quantity", 0);
Path of the first tab:
Path of the second unnecessary tab:
![grafik](https://github.com/microsoft/AL/assets/7450586/39d372a0-da80-4713-9dfb-532dc514f61b)
3. Expected behavior The vsx should notice that the dal file is already open and not open another dal file with the same name (but other path).
4. Actual behavior It just opens a new tab with the same content.
5. Versions: