User forums > Using Code::Blocks

Keyboard shortcut and C::B translation problem

<< < (4/4)

Pecan:

--- Quote from: oBFusCATed on June 14, 2019, 10:09:57 pm ---I don't like that Next call tip will be ctrl-n and prev call tip would be ctrl-shift-p. I'd rather change both. Or just remove the shortcuts. I didn't know these existed, I'm using up and down arrows, they work just fine, not sure what is the benefit of using the shortcuts.

--- End quote ---

Ok, just get rid of them if nobody else objects. I've never used them myself.
It's also probable that nobody else uses them either, since there's been no complaints that they don't work.

gd_on:
In menuutils.cpp, line 940 and 941 there is the same string. The extracting tool using xgettext see these two lines as only one, with twice the same string proposed for translation and separated by a \n. In this case, in a wxASSERT, I suppose that only the english string is needed, not the translated one. May be a better code could be :

--- Code: ---    wxASSERT_MSG(data == NULL,
                wxT("wxMenuShortcutWalker does not use the 'data' parameter") // English only.
        );

--- End code ---

and keep wxT (or _T) to be wx 2.8 compatible.

gd_on

Pecan:

--- Quote from: gd_on on June 15, 2019, 02:41:40 pm ---In menuutils.cpp, line 940 and 941 there is the same string. The extracting tool using xgettext see these two lines as only one, with twice the same string proposed for translation and separated by a \n. In this case, in a wxASSERT, I suppose that only the english string is needed, not the translated one. May be a better code could be :

--- Code: ---    wxASSERT_MSG(data == NULL,
                wxT("wxMenuShortcutWalker does not use the 'data' parameter") // English only.
        );

--- End code ---

and keep wxT (or _T) to be wx 2.8 compatible.

gd_on

--- End quote ---
Fixed head rev 11742

Navigation

[0] Message Index

[*] Previous page