Kaydet (Commit) 532dee5f authored tarafından Tor Lillqvist's avatar Tor Lillqvist

Add comment about the ugly hardcoded resource ids

Change-Id: I54d04f97fe720d6a262a86b63126f328a7812018
üst a9f03c1a
...@@ -65,9 +65,21 @@ struct ResIdToResName ...@@ -65,9 +65,21 @@ struct ResIdToResName
static const ResIdToResName pToolBarResToName[] = static const ResIdToResName pToolBarResToName[] =
{ {
{ 558, "fullscreenbar" }, // OMG! hardcoded numbers that have nice (?) symbolic names
{ 560, "standardbar", }, // elsewhere.
{ 18001, "formsnavigationbar" }, { 558, "fullscreenbar" }, // This 558 for instance equals RID_FULLSCREENTOOLBOX (in
// value, and presumably also in semantics) from app.hrc in
// this very same directory, so why RID_FULLSCREENTOOLBOX
// can't be used I have no idea.
{ 560, "standardbar", }, // 560 is called RID_ENVTOOLBOX in app.hrc, still the same?
{ 18001, "formsnavigationbar" }, // Probably the rest are defined in .hrc files that are higher
// up in the dependency chain and/or later in the build order,
// and that is the (bad) reason why their symbolic names are
// not available? Would it really be so owful to move the .hrc
// files in question out from the modules where they now are?
{ 18002, "formsfilterbar" }, { 18002, "formsfilterbar" },
{ 18003, "formtextobjectbar" }, { 18003, "formtextobjectbar" },
{ 18004, "formcontrols" }, { 18004, "formcontrols" },
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment