Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
small enhancement to statusbar - show current position of caret
White-Tiger:
weird enough... a byte position usually used with binary files is useful enough for a C/C++ IDE, but a string (selection) length isn't even though it's hard to develop in C/C++ without it... (in a meaningful way without relying on strcpy(), std:: etc.)
oBFusCATed:
I don't understand your comment. Can you clarify what do you mean with it?
If you ask me I'd never use this position, so I can't comment on the usefulness of the feature.
There was a patch, the author reminded me, I've looked at it and I've committed it.
Your patch has not been rejected, so if you've reminded us we could have applied it first.
Now if your patch differs to the one applied in behaviour you'll need to provide a configuration option or negotiate with the patch author that your behaviour is better and provide a patch to change the behaviour.
White-Tiger:
no.. my patch added a different kind of thing... yet it's now a merge conflict of course..
If there is a "configuration" option to add.. it would have to be a customizable as in a custom format string to be applied.. Which also means to have a meaningful default.
Also, I didn't try to neglect the use of a binary position, it's just that I wouldn't assume to edit binary files through an IDE... (and yes, those could be text files as well as with the CC example)
What might work as well, is different presets for the status bar row... like cycling through possible "sets" by clicking them...
oBFusCATed:
I don't think a custom format string is needed or worth it. Just make the most obvious combinations.
I'm not sure what is better - adding a button like the highlight language button or just adding a configuration option in the settings.
The buttons in the status bar are looking pretty bad when using wx3.x on linux (not sure what is the behaviour on windows). I'll have to investigate this anyway...
LETARTARE:
Hello,
I find that with this change, the place to see the full path of the current file is reduced.
It seems to me more useful to see the path of the file used this change (See attached image)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version