Slick-C stack when removing tool

[rjpontefract]

I had 2 occurences of a Test tool under the tools tab of the project properties dialog. Both were configured to execute "mvn test". I highlighed the second one and clicked the red X to delete it. The following stack was the result and the tool wasn't removed:

Stack trace written to file: C:\Users\PONTEF~1\AppData\Local\Temp\vsstack.
Variable element or variable not initialized
project.ex 20179 _project_form.ctlToolTree.on_change(10,10) p_window_id: 2509 p_object: OI_CHECK_BOX p_name: ctlToolClearProcessBuf
project.ex 8115 _project_form.ctlToolDelete.lbutton_up() p_window_id: 2621 p_object: OI_IMAGE p_name: ctlToolDelete
picture.ex 2516 _ul2_picture.lbutton_down(0) p_window_id: 2501 p_object: OI_EDITOR p_name:
picture.ex 3000 _ul2_imageb.lbutton_down(0) p_window_id: 2501 p_object: OI_EDITOR p_name:
dlgeditv.ex 7260 show(-mdi -modal -xy _project_form,C:\RJPTest\RJPTestService3Impl\RJPTestService3Impl.vpj,189,,1,1,0,0) p_window_id: 2101 p_object: OI_TREE_VIEW p_name: _proj_tooltab_tree
project.ex 614 project:project_edit2(,C:\RJPTest\RJPTestService3Impl\RJPTestService3Impl.vpj,0) p_window_id: 1627 p_object: OI_EDITOR p_name: _shellEditor
project.ex 790 project_edit(,0) p_window_id: 1627 p_object: OI_EDITOR p_name: _shellEditor


2021-09-19T21:28:26+0000

SlickEdit Pro 2021 (v26.0.0.3 64-bit Qt5)

Serial number: FE26820_BETA
License type: Beta License
License expiration: 2021-10-10 13:00:00
License file: C:\ProgramData\slickedit\26\slickedit.lic

Build Date: September 1, 2021
Emulation: Visual Studio

OS: Windows 10 x64
OS Version: 10.00.0
Memory: 78% Load, 25638MB/32502MB Physical, 23231MB/37366MB Page File, 7743MB/134217727MB Virtual
Shell Information: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 1920 x 1080 (-1920 -17 1920 1080), 1920 x 1080 (0 0 1920 1080), 1920 x 1080 (1920 5 1920 1080)

Project Type: Java
Language: .java (Java)
Encoding: ACP (1252)

Installation Directory: C:\Program Files\SlickEdit Pro 26.0.0 Beta3\ (non-removable drive,NTFS,91809MB free)
Configuration Directory: C:\Users\pontefractr\Documents\My SlickEdit Config\26.0.0\ (non-removable drive,NTFS,91809MB free)
Migrated from: C:\Users\pontefractr\Documents\My SlickEdit Config\25.0.2\

[Clark]

How did you get two occurrences of the same tool? The GUI won't allow this. Did you manually add these?

I was able to reproduce this stack if I edited my .vpj file and added two copies of the same tool.

[rjpontefract]

Hi Clark
I have no idea, I just imported a maven project from its pom.xml file.  I didn't add any tools using the GUI or by editing the project file.  I noticed that there were two occurrences of the "test" tool, so I tried to delete one of them.

[patrick]

I haven't been able to get this to happen, but there's only one place where we edit the project tasks/menu after the standard maven project template has been expanded, so the bug is probably in there.   Are the duplicates right next to other in the menu, or is some other item in between them?

In the meantime, I think the only way you can clear out the duplicate tool is to edit your .vpj file and delete one of the <Target> tags with the attribute Name="test".

[rjpontefract]

The duplicates are next to each other, but looking at the project I just imported, they seem to be multiplying.

[patrick]

Having multiple duplicates torpedos my original idea.  Down to more unlikely candidates.  Definitely let me know if you seem to get any more duplicates without doing another import.

Also, maybe a long shot, but can you post your user.cfg.xml file from your configuration directory?  ("C:\Users\pontefractr\Documents\My SlickEdit Config\26.0.0\")   

[rjpontefract]

Hi Patrick
I'd prefer not to post user.cfg.xml publicly, is there a way to share it with you privately?

[patrick]

Sure, I'll PM you the details.

[patrick]

I got your PM yesterday, but I haven't had any luck reproducing the problem.   It's a very odd one.  For the maven import, we expand a project template and then we don't do any further editing of the project file (with one exception I'll get to later).   So the vpj is created with the same mechanism used by New Project.  So I don't expect that to be doing anything weird, and I've looked it over and also the Maven project template we ship. 

The one exception is when you're re-opening a Maven project that was imported pre-v19 I believe and then it will add the Maven Options entry to the project/Build-menu.  I don't think that's the case here, and I've tested and gone through that code, and it seems to be ok.  These are newly imported Maven projects, correct?

If you've still got a project that's displaying more than one test entry, can you upload the project's .vpj file?  Use the same case number as for the previous upload, with a "2" appended to the end.

[rjpontefract]

Hi Patrick
I've uploaded a vpj file as case "duplicatemenus2".  Hope it helps.