Advanced MFC Programming

More documents

Recommendations

Info

Chapter 16. Context Sensitive Help Figure 16-4. Create a footnote in Microsoft Word Tag “help_test_A” can be referenced either from other footnote pages or from the application. If we want to let the user jump from one help item to another (for example, when viewing help on “telp_test_A”, the user may want to jump to footnote “help_test_B” by clicking on a link within the same page), we need to implement links by editing the “.rtf” file. Suppose we have added four footnotes for the newly implemented commands: “help_test_A”, “help_test_B”, “help_test_C”, and “help_test_D”, and we want to add links to the rest of three commands within each footnote page. For example, help item “help_test_A” may be implemented as illustrated in Figure 16-5: Figure 16-5. Help page for command ID_HELPTEST_TESTA Under “See Also” statement, there are three links that will direct mouse clicking to footnotes “help_test_B”, “help_test_C” and “help_test_D”. To create this type of links, we need to use special font format. We need to use double underline style to format the text that will be linked to a footnote (By doing this, the text formatted with double underline can respond to mouse clicking and bringing up another help item). Following the underlined text, we need to place the footnote tag using “Hidden” font style. To let the hidden text be displayed in the Word editor, we can execute command Tools | Options… and click tab View on the popped up property sheet. Then within “Nonprinting Characters” section, check “Hidden Text” check box. Now we can make a link very easily. First we need to type in and format the text as illustrated in Figure 16-6: Figure 16-6. Create link within a help item To format text using double underline, we can select the text, then execute command Format | Font…. From the popped up property sheet, we can go to “Font” page and select “Double” form “Underline” combo box. By doing this, the selected text will be double underlined. To format text using “Hidden Text” style, we can first select the text, then execute command Format | Font…, go to “Font” 484
Chapter 16. Context Sensitive Help page, make sure that “None” is selected from the “Underline” combo box, and check “Hidden” check box within “Effects” section. ID Mapping In order to support context sensitive help, we must link the footnotes to their corresponding command IDs. In our case, we need to link “help_test_A” to ID_HELPTEST_TESTA, “help_test_B” to ID_HELPTEST_TESTB… and so on. This ID mappings are implemented in “.hm” file, so by opening file “Help.hm” with a text editor, we will see all the IDs of the help items supported in the sample. Generally help IDs are generated according to certain rules: it bases the help ID of a control (or a window) on its resource ID. By default, for a command whose ID starts with “ID_”, MFC generates symbolic help ID by prefixing a character ‘H’ to the resource ID. For example, for command ID_HELPTEST_TESTA, the help ID generated by MFC is HID_HELPTEST_TESTA. For the actual ID value, MFC generates it by adding a fixed number to the corresponding resource ID value. For example, if the value of ID_HELPTEST_TESTA is 0x8004, the value of HID_HELPTEST_TESTA would be 0x18004 ⎯ here a number of 0x1000 is added to the command resource ID. By doing this, when the user executes a command in the help mode (When the mouse cursor changes to a question mark after the user clicks command ID_CONTEXT_HELP), the application will first find out the resource ID of the command being executed, add a fixed value, then pass the result to the help. By using this rule to generate ID for a help item, it is easier for us to implement context-sensitive help. Although the ID mapping is customizable, which means we can prefix different character(s) to a resource ID for generating help ID (For example, the help ID of command ID_HELPTEST_TESTA could be HLID_HELPTEST_TESTA), and we can add any value to the resource ID to generate a help ID, it is more convenient if we stick to the rules of MFC. For example, if we add 0x20000 instead of 0x10000 to the resource ID to make a help ID, we also need to add some code to the program to customize its default behavior. Another problem still remains: since we’ve already added footnotes and defined our own tags, the command IDs are still not directly linked to the footnote tags. For example, the help ID of command ID_HELPTEST_TESTA is HID_HELPTEST_TESTA, while the footnote tag implemented in the help file is “help_test_A”. This can be solved by defining alias names in the help project file. By opening “*.HPJ” file, we will see an [ALIAS] session. Under this session, a help ID can be linked directly to a footnote tag. In our case, the footnote tags are “help_test_A”, “help_test_B”…, and the help IDs automatically generated by MFC are HID_HELPTEST_TESTA, HID_HELPTEST_TESTB…. To link them together, we can add the following to alias session: …… [ALIAS] HID_HELPTEST_TESTA=help_test_A HID_HELPTEST_TESTB=help_test_B HID_HELPTEST_TESTC=help_test_C HID_HELPTEST_TESTD=help_test_D Obviousely, if we use the default help ID strings to implement footnote tags (i.e., use HID_HELPTEST_TESTA instead of help_test_A as the footnote tag), the ID mapping could be eleminated. By doing this, when the user executes certain command in the help mode, the corresponding help page will be automatically brought up. Help Topics Dialog Box The footnotes can also be referenced from “Help Topics” dialog box. This dialog box is activated when the user executes command ID_HELP_FINDER. The contents contained in “Help Topics” dialog box are stored in “.cnt” file. To edit this file, we can open it using Help Workshop. In the Help Workshop, we can add two types of items: Heading and Tab Entry. A heading will not be linked to any footnote. Under each heading, we can add several tab entries, which need to be linked to footnotes. A new item can be added by clicking buttons labeled “Add Above…”, “Add Below…”. After that, a dialog box will pop up asking us to input the description text as well as the help ID (the footnote tag). The description of an item 485
Page 1 and 2:
Advanced MFC Programming Supporting
Page 3 and 4:
Checking a Menu Item 2.2 Right Clic
Page 5 and 6:
Trapping Double Clicking Message Re
Page 7 and 8:
COMMON DIALOG BOXES 7.1 File Open a
Page 9 and 10:
9.1 Outputting Text Using Different
Page 11 and 12:
Summary SAMPLE: SIMPLE PAINT 11.0 P
Page 13 and 14:
13.2 Creating Applications without
Page 15 and 16:
Functions Implementing Comparisons
Page 17 and 18:
Chapter 1. Tool Bar and Dialog Bar
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Chapter 2. Menu Chapter 2 Menu Menu
Page 51 and 52:
Chapter 2. Menu ON_COMMAND(ID_EDIT_
Page 53 and 54:
Chapter 2. Menu “clipboard”. We
Page 55 and 56:
Chapter 2. Menu Using Class CMenu W
Page 57 and 58:
Chapter 2. Menu } After implementin
Page 59 and 60:
Chapter 2. Menu ); UINT nPosition,
Page 61 and 62:
Chapter 2. Menu void CMenuDoc::OnEd
Page 63 and 64:
Chapter 2. Menu } In the sample, bi
Page 65 and 66:
Chapter 2. Menu Message Mapping for
Page 67 and 68:
Chapter 2. Menu We can implement bi
Page 69 and 70:
Chapter 2. Menu CDC *ptrDC; CDC dcM
Page 71 and 72:
Chapter 2. Menu Because the popup m
Page 73 and 74:
Chapter 3. Splitter Window Chapter
Page 75 and 76:
Chapter 3. Splitter Window function
Page 77 and 78:
Chapter 3. Splitter Window BOOL CSp
Page 79 and 80:
Chapter 3. Splitter Window In the a
Page 81 and 82:
Chapter 3. Splitter Window Sample S
Page 83 and 84:
Chapter 3. Splitter Window WM_LBUTT
Page 85 and 86:
Chapter 4. Button Chapter 4 Buttons
Page 87 and 88:
Chapter 4. Button Use string text a
Page 89 and 90:
Chapter 4. Button function, first t
Page 91 and 92:
Chapter 4. Button Now we can remove
Page 93 and 94:
Chapter 4. Button } ( m_bBmpCheck ?
Page 95 and 96:
Chapter 4. Button using bit-wise AN
Page 97 and 98:
Chapter 4. Button Overriding Functi
Page 99 and 100:
Chapter 4. Button …… First pBit
Page 101 and 102:
Chapter 4. Button Using Class MCBit
Page 103 and 104:
Chapter 4. Button The button’s ID
Page 105 and 106:
Chapter 4. Button However, since me
Page 107 and 108:
Chapter 4. Button Here, we use subc
Page 109 and 110:
Chapter 5. Common Controls command
Page 111 and 112:
Chapter 5. Common Controls ((CSpinB
Page 113 and 114:
Chapter 5. Common Controls } The in
Page 115 and 116:
Chapter 5. Common Controls …… B
Page 117 and 118:
Chapter 5. Common Controls The “S
Page 119 and 120:
Chapter 5. Common Controls button
Page 121 and 122:
Chapter 5. Common Controls In this
Page 123 and 124:
Chapter 5. Common Controls (CBN_CLO
Page 125 and 126:
Chapter 5. Common Controls compare
Page 127 and 128:
Chapter 5. Common Controls } ptrEdi
Page 129 and 130:
Chapter 5. Common Controls ……
Page 131 and 132:
Chapter 5. Common Controls void CWn
Page 133 and 134:
Chapter 5. Common Controls Five loc
Page 135 and 136:
Chapter 5. Common Controls This fun
Page 137 and 138:
Chapter 5. Common Controls After cr
Page 139 and 140:
Chapter 5. Common Controls typedef
Page 141 and 142:
Chapter 5. Common Controls Using th
Page 143 and 144:
Chapter 5. Common Controls Paramete
Page 145 and 146:
Chapter 5. Common Controls void MCT
Page 147 and 148:
Chapter 5. Common Controls modifica
Page 149 and 150:
Chapter 5. Common Controls In funct
Page 151 and 152:
Chapter 5. Common Controls Changing
Page 153 and 154:
Chapter 5. Common Controls m_tabCtr
Page 155 and 156:
Chapter 5. Common Controls Custom R
Page 157 and 158:
Chapter 6. Dialog Box Chapter 6 Dia
Page 159 and 160:
Chapter 6. Dialog Box void CMLDialo
Page 161 and 162:
Chapter 6. Dialog Box } Function CP
Page 163 and 164:
Chapter 6. Dialog Box Everything is
Page 165 and 166:
Chapter 6. Dialog Box } MINMAXINFO;
Page 167 and 168:
Chapter 6. Dialog Box Sample Sampel
Page 169 and 170:
Chapter 6. Dialog Box } brush=(HBRU
Page 171 and 172:
Chapter 6. Dialog Box wndA.GetWindo
Page 173 and 174:
Chapter 6. Dialog Box rectStaticGrp
Page 175 and 176:
Chapter 6. Dialog Box } TOOLTIPTEXT
Page 177 and 178:
Chapter 6. Dialog Box ) { } if ( )
Page 179 and 180:
Chapter 6. Dialog Box pWndCtrl=GetW
Page 181 and 182:
Chapter 6. Dialog Box Sample 6.8-2\
Page 183 and 184:
Chapter 6. Dialog Box } // handle t
Page 185 and 186:
Chapter 6. Dialog Box 1) Tracking s
Page 187 and 188:
Chapter 7. Common Dialog Boxes DWOR
Page 189 and 190:
Chapter 7. Common Dialog Boxes } {
Page 191 and 192:
Chapter 7. Common Dialog Boxes } }
Page 193 and 194:
Chapter 7. Common Dialog Boxes dial
Page 195 and 196:
Chapter 7. Common Dialog Boxes Alth
Page 197 and 198:
Chapter 7. Common Dialog Boxes } NU
Page 199 and 200:
Chapter 7. Common Dialog Boxes Stc3
Page 201 and 202:
Chapter 7. Common Dialog Boxes DWOR
Page 203 and 204:
Chapter 7. Common Dialog Boxes the
Page 205 and 206:
Chapter 7. Common Dialog Boxes Comm
Page 207 and 208:
Chapter 7. Common Dialog Boxes Retr
Page 209 and 210:
Chapter 7. Common Dialog Boxes 7.9
Page 211 and 212:
Chapter 7. Common Dialog Boxes } }
Page 213 and 214:
Chapter 7. Common Dialog Boxes …
Page 215 and 216:
Chapter 7. Common Dialog Boxes …
Page 217 and 218:
Chapter 8. DC, Pen, Brush and Palet
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Chapter 9. Font Here, member lfFace
Page 255 and 256:
Chapter 9. Font } dlg.m_bBgdStyle=m
Page 257 and 258:
Chapter 9. Font The first element o
Page 259 and 260:
Chapter 9. Font int CALLBACK EnumFo
Page 261 and 262:
Chapter 9. Font for(i=0; iGetSafeHa
Page 263 and 264:
Chapter 9. Font }; Variable m_nRang
Page 265 and 266:
Chapter 9. Font Frame border is gra
Page 267 and 268:
Chapter 9. Font CFont *ptrFont; if(
Page 269 and 270:
Chapter 9. Font POINT pt; CClientDC
Page 271 and 272:
Chapter 9. Font } if(dlg.DoModal()
Page 273 and 274:
Chapter 9. Font In this function, W
Page 275 and 276:
Chapter 9. Font } CScrollView::OnKe
Page 277 and 278:
Chapter 9. Font …… } nKeyState=
Page 279 and 280:
Chapter 9. Font To check out if the
Page 281 and 282:
Chapter 9. Font the same, it indica
Page 283 and 284:
Chapter 9. Font } if(m_nSelIndexBgn
Page 285 and 286:
Chapter 9. Font GHND GPTR Same with
Page 287 and 288:
Chapter 9. Font …… } { Since th
Page 289 and 290:
Chapter 9. Font Function CDocument:
Page 291 and 292:
Chapter 9. Font …… void CGDIDoc
Page 293 and 294:
Chapter 9. Font …… { } UpdateAl
Page 295 and 296:
Chapter 9. Font …… …… case
Page 297 and 298:
Chapter 9. Font client window to be
Page 299 and 300:
Chapter 10. Bitmap ); DWORD dwRop T
Page 301 and 302:
Chapter 10. Bitmap Sample 10.1-2\GD
Page 303 and 304:
Chapter 10. Bitmap The next part of
Page 305 and 306:
Chapter 10. Bitmap Sample Sample 10
Page 307 and 308:
Chapter 10. Bitmap } pPalDraw=pDoc-
Page 309 and 310:
Chapter 10. Bitmap Member bfType mu
Page 311 and 312:
Chapter 10. Bitmap …… dwSize=bf
Page 313 and 314:
Chapter 10. Bitmap …… …… }
Page 315 and 316:
Chapter 10. Bitmap Now the size of
Page 317 and 318:
Chapter 10. Bitmap fuColorUse Speci
Page 319 and 320:
Chapter 10. Bitmap if(hData != NULL
Page 321 and 322:
Chapter 10. Bitmap …… …… cl
Page 323 and 324:
Chapter 10. Bitmap used as the orig
Page 325 and 326:
Chapter 10. Bitmap With the above i
Page 327 and 328:
Chapter 10. Bitmap …… …… if
Page 329 and 330:
Chapter 10. Bitmap …… } } { if(
Page 331 and 332:
Chapter 10. Bitmap …… } rgbQuad
Page 333 and 334:
Chapter 10. Bitmap DIB Section Both
Page 335 and 336:
Chapter 10. Bitmap } } if(m_pBmpMas
Page 337 and 338:
Chapter 10. Bitmap …… m_pBmpOld
Page 339 and 340:
Chapter 10. Bitmap BITMAP bm; …
Page 341 and 342:
Chapter 10. Bitmap Draw this portio
Page 343 and 344:
Chapter 10. Bitmap 1) Paint the des
Page 345 and 346:
Chapter 10. Bitmap color bitmap, bu
Page 347 and 348:
Chapter 10. Bitmap will destroy the
Page 349 and 350:
Chapter 10. Bitmap 10) The total im
Page 351 and 352:
Chapter 11. Sample: Simple Paint Af
Page 353 and 354:
Chapter 11. Sample: Simple Paint CG
Page 355 and 356:
Chapter 11. Sample: Simple Paint Th
Page 357 and 358:
Chapter 11. Sample: Simple Paint Co
Page 359 and 360:
Chapter 11. Sample: Simple Paint vo
Page 361 and 362:
Chapter 11. Sample: Simple Paint m_
Page 363 and 364:
Chapter 11. Sample: Simple Paint cu
Page 365 and 366:
Chapter 11. Sample: Simple Paint Te
Page 367 and 368:
Chapter 11. Sample: Simple Paint
Page 369 and 370:
Chapter 11. Sample: Simple Paint CS
Page 371 and 372:
Chapter 11. Sample: Simple Paint fu
Page 373 and 374:
Page 375 and 376:
Chapter 11. Sample: Simple Paint DW
Page 377 and 378:
Chapter 11. Sample: Simple Paint m_
Page 379 and 380:
Chapter 11. Sample: Simple Paint co
Page 381 and 382:
Page 383 and 384:
Chapter 11. Sample: Simple Paint Ho
Page 385 and 386:
Chapter 11. Sample: Simple Paint 1)
Page 387 and 388:
Chapter 12. Screen Capturing & Prin
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Chapter 13. Adding Special Features
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Chapter 14. Views ID_EDIT_PASTE pas
Page 447 and 448:
Chapter 14. Views Another feature o
Page 449 and 450: Chapter 14. Views szFind=newName; s
Page 451 and 452: Chapter 14. Views ON_COMMAND(ID_BUT
Page 453 and 454: Chapter 14. Views IDB_BITMAP_CLOSEF
Page 455 and 456: Chapter 14. Views Because we do not
Page 457 and 458: Chapter 14. Views For the root dire
Page 459 and 460: Chapter 14. Views The columns are a
Page 461 and 462: Chapter 14. Views } ff.Close(); Des
Page 463 and 464: Chapter 14. Views …… …… if(
Page 465 and 466: Chapter 14. Views void CDirView::Ad
Page 467 and 468: Chapter 14. Views Actually, in the
Page 469 and 470: Chapter 14. Views } if(szName1.GetL
Page 471 and 472: Chapter 14. Views Mouse Cursor Coor
Page 473 and 474: Chapter 16. Context Sensitive Help
Page 499: Chapter 16. Context Sensitive Help
Page 507 and 508: Appendix A. Virtual-key Codes Appen
Page 509 and 510: Appendix A. Virtual-key Codes Funct
Page 511 and 512: Appendix B. Ternary Raster Operatio
Page 517 and 518: Index Index #if, 416 #pragma, 416 .
Page 519 and 520: Index CDC::SetPixel, 321 CDC::SetRO
Page 521 and 522: Index CRectTracker, 345 CRectTracke
Page 523 and 524: Index CWnd::SetMenu, 55 CWnd::SetTi
Page 525 and 526: Index HBRUSH, 201 HCURSOR, 262 HDAT
Page 527 and 528: Index Background palette, 224 Chang
Page 529 and 530: Index Default tool bar, 1 Enable or
show all

Advanced MFC Programming

Create successful ePaper yourself

Delete template?

Save as template?