Closed GoogleCodeExporter closed 9 years ago
you can't remove internal commands, only hide them.
1. goto options
2. Select "Remove" on "Show System Files"
3. click "OK" button
4. "Show System Files" won't show up anymore on the toolbar.
Original comment by tortoisesvn
on 8 Jun 2009 at 2:38
I have done ;).
In the options Dialog it now has the "Activate" button instead of remove, but
the
"Show system files" still shows. The same goes for the "Rename" button. This is
disabled but also shows. I can provide screen shots if it will help further.
Thanks,
Dave
Original comment by goo...@taeguk.co.uk
on 8 Jun 2009 at 2:44
Works fine for me.
Try deleting the file %appdata%\stexbar\commands.ini
maybe your ini file got messed up somehow (make a copy of it first - if
deleting that
file fixes the issue, I'd be interested in your file so I can fix this when
loading
such a messed up file)
Original comment by tortoisesvn
on 8 Jun 2009 at 3:25
I've followed your advice and I have tried restarting Explorer but still an
issue I'm
affraid.
Here's the Command.ini for Show System Files:
[0003_Show system files]
alt=
commandline=INTERNALCOMMANDHIDDEN
control=true
fileselected=true
folderselected=true
icon=
keycode=72
name=Show system files
noselection=true
noviewpath=
selected=true
selectedcount=0
separator=
shift=true
viewpath=true
And the full "messed up file" as you call it ;)
http://taeguk.co.uk/Commands.ini
Dave
Original comment by goo...@taeguk.co.uk
on 8 Jun 2009 at 3:42
very strange. The "INTERNALCOMMANDHIDDEN" is correct: it tells that the command
should not be shown in the toolbar.
I've now tried this in an XP VM (I'm using Vista here) and I still can't
reproduce
this issue.
btw: your link to the Commands.ini file gives me a 404 :)
Original comment by tortoisesvn
on 8 Jun 2009 at 3:50
I'll try on my Home PC tonight (Not installed on there ATM) and I'll test on a
colleagues PC tomorrow and report back.
Link is : http://taeguk.co.uk/Commands.zip (silly ISP blocking .ini (and .7z))
Original comment by goo...@taeguk.co.uk
on 8 Jun 2009 at 3:56
add the commands.ini file to the issue
Original comment by tortoisesvn
on 8 Jun 2009 at 3:58
Attachments:
Tried your commands.ini file, and it worked also just fine on my machine here.
I don't know why this doesn't work for you...
Original comment by tortoisesvn
on 8 Jun 2009 at 6:04
Still not working at Home either. Really not sure what I've done :o.
Original comment by goo...@taeguk.co.uk
on 8 Jun 2009 at 10:09
Attachments:
Ups, I think I know why I can't reproduce this:
See issue #59 and r203.
Original comment by tortoisesvn
on 9 Jun 2009 at 4:52
Ah I see. Fixed, but not released :D.
I tried searching, but didn't find that one.
Dave
Original comment by goo...@taeguk.co.uk
on 9 Jun 2009 at 10:56
Original issue reported on code.google.com by
goo...@taeguk.co.uk
on 8 Jun 2009 at 12:39