I'd like feedback on this before I open a bug. I am using PSPad as the editor for the QVCS version control system. This works fine except for one thing.
I should note first that I run in "single instance" mode. With every other application, this opens all additional files in a new tab. This is the case if that file is an associated file (such as .txt files) that I open via double-click, or if I explicitly run something like 'pspad.exe newfile.php'. In either case, the file opens in a new tab. With QVCS, when I open the first file, it is opened okay. When I open a second file, however, I get TWO new file tabss. I get a 'dummy' tab that is empty (ie, creating a new file), and then I get a tab with the file I expected. I spoke with the QVCS developer, and he admits to populating arg[0]='dummy' with whatever API he's using to launch the viewer. I believe that's a error on his part, as I've never seen an API requiring explicit setting of the [0] element. However, PSPad is also the only editor I have that sees this 'dummy' argument. Also, if I take PSPad out of "single instance" mode, then I get a new window for each file and I never see the 'dummy' tab. This tells me there is something about the way PSPad is parsing the command tail while in single instance mode, combined with what I believe is QVCS's improper use of the arg[] array with the API call it is using -- the combination of the two resulting in the 'dummy' tab that I'm seeing. It's as if PSPad is processing the entire arg[] array (command tail) when opening secondary files. I suspect in normal situations this is okay, as [0] is probably not set. With QVCS, however, somehow [0]=dummy is getting though to PSPad as a legitimate command option. I'm still pursuing this with QVCS as their bug; however, do you think it should also be checked as a PSPad bug? Thanks! -- <http://forum.pspad.com/read.php?2,55081,55081> PSPad freeware editor http://www.pspad.com
