]>
Commit | Line | Data |
---|---|---|
1 | ///////////////////////////////////////////////////////////////////////////// | |
2 | // Name: tips.h | |
3 | // Purpose: topic overview | |
4 | // Author: wxWidgets team | |
5 | // RCS-ID: $Id$ | |
6 | // Licence: wxWindows license | |
7 | ///////////////////////////////////////////////////////////////////////////// | |
8 | ||
9 | /** | |
10 | ||
11 | @page overview_tips wxTipProvider Overview | |
12 | ||
13 | Many "modern" Windows programs have a feature (some would say annoyance) of | |
14 | presenting the user tips at program startup. While this is probably useless to | |
15 | the advanced users of the program, the experience shows that the tips may be | |
16 | quite helpful for the novices and so more and more programs now do this. For a | |
17 | wxWidgets programmer, implementing this feature is extremely easy. To show a | |
18 | tip, it is enough to just call wxShowTip function like this: | |
19 | ||
20 | @code | |
21 | if ( ...show tips at startup?... ) | |
22 | { | |
23 | wxTipProvider *tipProvider = wxCreateFileTipProvider("tips.txt", 0); | |
24 | wxShowTip(windowParent, tipProvider); | |
25 | delete tipProvider; | |
26 | } | |
27 | @endcode | |
28 | ||
29 | Of course, you need to get the text of the tips from somewhere - in the example | |
30 | above, the text is supposed to be in the file tips.txt from where it is read by | |
31 | the <em>tip provider</em>. The tip provider is just an object of a class | |
32 | deriving from wxTipProvider. It has to implement one pure virtual function of | |
33 | the base class: GetTip. In the case of the tip provider created by | |
34 | wxCreateFileTipProvider, the tips are just the lines of the text file. | |
35 | ||
36 | If you want to implement your own tip provider (for example, if you wish to | |
37 | hardcode the tips inside your program), you just have to derive another class | |
38 | from wxTipProvider and pass a pointer to the object of this class to | |
39 | wxShowTip - then you don't need wxCreateFileTipProvider at all. | |
40 | ||
41 | You will probably want to save somewhere the index of the tip last shown - so | |
42 | that the program doesn't always show the same tip on startup. As you also need | |
43 | to remember whether to show tips or not (you shouldn't do it if the user | |
44 | unchecked "Show tips on startup" checkbox in the dialog), you will probably | |
45 | want to store both the index of the last shown tip (as returned by | |
46 | wxTipProvider::GetCurrentTip and the flag telling whether to show the tips at | |
47 | startup at all. | |
48 | ||
49 | In a tips.txt file, lines that begin with a # character are considered comments | |
50 | and are automatically skipped. Blank lines and lines only having spaces are | |
51 | also skipped. | |
52 | ||
53 | You can easily add runtime-translation capacity by placing each line of the | |
54 | tips.txt file inside the usual translation macro. For example, your tips.txt | |
55 | file would look like this: | |
56 | ||
57 | @code | |
58 | _("This is my first tip") | |
59 | _("This is my second tip") | |
60 | @endcode | |
61 | ||
62 | Now add your tips.txt file into the list of files that gettext searches for | |
63 | translatable strings. The tips will thus get included into your generated .po | |
64 | file catalog and be translated at runtime along with the rest of your | |
65 | application's translatable strings. | |
66 | ||
67 | @note Each line in the tips.txt file needs to strictly begin with exactly the 3 | |
68 | characters of underscore-parenthesis-doublequote, and end with | |
69 | doublequote-parenthesis, as shown above. Also, remember to escape any | |
70 | doublequote characters within the tip string with a backslash-doublequote. | |
71 | ||
72 | See the dialogs program in your samples folder for a working example inside a | |
73 | program. | |
74 | ||
75 | */ | |
76 |