Development/Tutorials/Games/Highscores - Revision history

Neverendingo: Text replace - "`" to ""`


2011-06-29T19:34:56Z
Text replace - "<code cppqt n>" to "<syntaxhighlight lang="cpp-qt" line>"

				
				
				
				
			
			← Older revision
			Revision as of 19:34, 29 June 2011
			
Line 25:
Line 25:
  ==Displaying Scores==   ==Displaying Scores==
  To display the high score table, it's as simple as two lines of code.     To display the high score table, it's as simple as two lines of code.  
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 37:
Line 37:
    
  In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.   In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KStandardGameAction>   #include <KStandardGameAction>
  void setupActions()   void setupActions()
Line 51:
Line 51:
  ===Simplest way to add a score===   ===Simplest way to add a score===
  The simplest way to add a new score to the table is as follows:   The simplest way to add a new score to the table is as follows:
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 71:
Line 71:
  ===Passing name by code===   ===Passing name by code===
  If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:   If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 87:
Line 87:
    
  And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:   And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 105:
Line 105:
  ===Custom fields===   ===Custom fields===
  Since there are only a set number of standard fields it is possible to add your own custom fields. For example you may want to put the number of moves the player made to the table. This is done through the <tt>KScoreDialog::addField()</tt> function.   Since there are only a set number of standard fields it is possible to add your own custom fields. For example you may want to put the number of moves the player made to the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 127:
Line 127:
  ==Grouping Scores==   ==Grouping Scores==
  Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:   Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>
    
Line 147:
Line 147:
    
  While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, it is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.   While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, it is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
− <code cppqt n> + <syntaxhighlight lang="cpp-qt" line>
  #include <KScoreDialog>   #include <KScoreDialog>

`Neverendingo: Text replace - "`" to ""

2011-06-29T19:16:06Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T19:13:46Z
Text replace - "<code cppqt>" to "<syntaxhighlight lang="cpp-qt">"

				
				
				
				
			
			← Older revision
			Revision as of 19:13, 29 June 2011
			
Line 64:
Line 64:
    
  However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:   However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  if(ksdialog.addScore(playersScore))   if(ksdialog.addScore(playersScore))
     ksdialog.exec();      ksdialog.exec();



Icwiener: /* Custom fields */ typo
2009-04-20T12:19:27Z
‎Custom fields:  typo

				
				
				
				
			
			← Older revision
			Revision as of 12:19, 20 April 2009
			
Line 104:
Line 104:
  </code>   </code>
  ===Custom fields===   ===Custom fields===
− Since there are only a set number of standard fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function. + Since there are only a set number of standard fields it is possible to add your own custom fields. For example you may want to put the number of moves the player made to the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
  <code cppqt n>   <code cppqt n>
  #include <KScoreDialog>   #include <KScoreDialog>





Icwiener: /* Custom fields */ typo
2009-04-20T12:18:40Z
‎Custom fields:  typo

				
				
				
				
			
			← Older revision
			Revision as of 12:18, 20 April 2009
			
Line 104:
Line 104:
  </code>   </code>
  ===Custom fields===   ===Custom fields===
− Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function. + Since there are only a set number of standard fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
  <code cppqt n>   <code cppqt n>
  #include <KScoreDialog>   #include <KScoreDialog>



Icwiener: /* Hiding Fields */ typo
2009-02-12T02:07:05Z
‎Hiding Fields:  typo

				
				
				
				
			
			← Older revision
			Revision as of 02:07, 12 February 2009
			
Line 146:
Line 146:
  In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.   In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.
    
− While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes. + While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, it is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
  <code cppqt n>   <code cppqt n>
  #include <KScoreDialog>   #include <KScoreDialog>



Milliams: No longer encessary. FindLibKDEGames.cmake is fixed
2008-05-03T21:07:21Z
No longer encessary. FindLibKDEGames.cmake is fixed

				
				
				
				
			
			← Older revision
			Revision as of 21:07, 3 May 2008
			
Line 26:
Line 26:
  To display the high score table, it's as simple as two lines of code.     To display the high score table, it's as simple as two lines of code.  
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  void showHighscores()   void showHighscores()
Line 38:
Line 38:
  In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.   In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
  <code cppqt n>   <code cppqt n>
− #include <KDE/KStandardGameAction> + #include <KStandardGameAction>
  void setupActions()   void setupActions()
  {   {
Line 52:
Line 52:
  The simplest way to add a new score to the table is as follows:   The simplest way to add a new score to the table is as follows:
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  void newHighscore(int playersScore)   void newHighscore(int playersScore)
Line 88:
Line 88:
  And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:   And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  void newHighscore(int score, const QString& name, int level)   void newHighscore(int score, const QString& name, int level)
Line 106:
Line 106:
  Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.   Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  void newHighscore(int score, const QString& name, int numMoves)   void newHighscore(int score, const QString& name, int numMoves)
Line 128:
Line 128:
  Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:   Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  void newHighscore(int playersScore)   void newHighscore(int playersScore)
Line 148:
Line 148:
  While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.   While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
  <code cppqt n>   <code cppqt n>
− #include <KDE/KScoreDialog> + #include <KScoreDialog>
    
  // timeString is a nicely formatted string   // timeString is a nicely formatted string



Milliams at 20:45, 28 April 2008
2008-04-28T20:45:24Z


				
				
				
				
			
			← Older revision
			Revision as of 20:45, 28 April 2008
			
Line 167:
Line 167:
    
  [[Category:C++]]   [[Category:C++]]
  + [[Category:KDEGames]]





Milliams: /* Grouping Scores */
2008-04-27T16:20:09Z
‎Grouping Scores

				
				
				
				
			
			← Older revision
			Revision as of 16:20, 27 April 2008
			
Line 130:
Line 130:
  #include <KDE/KScoreDialog>   #include <KDE/KScoreDialog>
    
− void newHighscore(int playersScore, const QString& difficulty) + void newHighscore(int playersScore)
  {   {
     KScoreDialog ksdialog(KScoreDialog::Name, this);      KScoreDialog ksdialog(KScoreDialog::Name, this);
−    ksdialog.setConfigGroup(difficulty); +    ksdialog.setConfigGroup(I18N_NOOP("Easy"));
     ksdialog.addScore(playersScore);      ksdialog.addScore(playersScore);
     ksdialog.exec();      ksdialog.exec();
Line 139:
Line 139:
  </code>   </code>
  Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.   Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.
  + 
  + A very important point to remember is to pass the untranslated group name through <tt>I18N_NOOP()</tt> otherwise the group name will not be translated properly and will cause bugs.
    
  ==Advanced Features==   ==Advanced Features==





Milliams: Correct include path
2008-04-12T22:32:40Z
Correct include path

				
				
				
				
			
			← Older revision
			Revision as of 22:32, 12 April 2008
			
Line 26:
Line 26:
  To display the high score table, it's as simple as two lines of code.     To display the high score table, it's as simple as two lines of code.  
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  void showHighscores()   void showHighscores()
Line 38:
Line 38:
  In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.   In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
  <code cppqt n>   <code cppqt n>
− #include <KStandardGameAction> + #include <KDE/KStandardGameAction>
  void setupActions()   void setupActions()
  {   {
Line 52:
Line 52:
  The simplest way to add a new score to the table is as follows:   The simplest way to add a new score to the table is as follows:
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  void newHighscore(int playersScore)   void newHighscore(int playersScore)
Line 88:
Line 88:
  And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:   And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  void newHighscore(int score, const QString& name, int level)   void newHighscore(int score, const QString& name, int level)
Line 106:
Line 106:
  Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.   Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  void newHighscore(int score, const QString& name, int numMoves)   void newHighscore(int score, const QString& name, int numMoves)
Line 128:
Line 128:
  Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:   Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  void newHighscore(int playersScore, const QString& difficulty)   void newHighscore(int playersScore, const QString& difficulty)
Line 146:
Line 146:
  While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.   While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
  <code cppqt n>   <code cppqt n>
− #include <KScoreDialog> + #include <KDE/KScoreDialog>
    
  // timeString is a nicely formatted string   // timeString is a nicely formatted string

@@ Line 33: / Line 33: @@
    ksdialog.exec();
+}
-</code>
+</syntaxhighlight>
 This will display the highscore table showing, by default, the 'Name' and 'Score' columns.
@@ Line 46: / Line 46: @@
    setupGUI();
+}
-</code>
+</syntaxhighlight>
 ==Adding Scores==
@@ Line 60: / Line 60: @@
    ksdialog.exec();
+}
-</code>
+</syntaxhighlight>
 This will add the score <tt>playersScore</tt> to the high score table and then launch the dialog. If it is the first score to be entered on the table, a blank line-edit will be provided for the player to enter their name, otherwise the line-edit will still be provided but the player's name will be automatically filled in.
@@ Line 67: / Line 67: @@
 if(ksdialog.addScore(playersScore))
    ksdialog.exec();
-</code>
+</syntaxhighlight>
 ===Passing name by code===
@@ Line 84: / Line 84: @@
    ksdialog.addScore(scoreInfo);
+}
-</code>
+</syntaxhighlight>
 And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
@@ Line 102: / Line 102: @@
    ksdialog.addScore(scoreInfo);
+}
-</code>
+</syntaxhighlight>
 ===Custom fields===
 Since there are only a set number of standard fields it is possible to add your own custom fields. For example you may want to put the number of moves the player made to the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
@@ Line 122: / Line 122: @@
    ksdialog.addScore(scoreInfo);
+}
-</code>
+</syntaxhighlight>
 The first argument to <tt>KScoreDialog::addField()</tt> must be from <tt>KScoreDialog::Custom1</tt> to <tt>KScoreDialog::Custom5</tt>, the second is the text that will appear on the high score table at the head of the column (and must therefore be i18n'd) and the last argument is a unique identifier for the field. After that, it is added to your <tt>KScoreDialog::FieldInfo</tt> in the same way as before.
@@ Line 137: / Line 137: @@
    ksdialog.exec();
+}
-</code>
+</syntaxhighlight>
 Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.
@@ Line 164: / Line 164: @@
    ksdialog.exec();
+}
-</code>
+</syntaxhighlight>
 [[Category:C++]]
 [[Category:KDEGames]]

← Older revision		Revision as of 20:45, 28 April 2008
Line 167:		Line 167:

	[[Category:C++]]		[[Category:C++]]
		+	[[Category:KDEGames]]

Development/Tutorials/Games/Highscores - Revision history

Neverendingo: Text replace - "" to ""

Neverendingo: Text replace - "" to ""

Neverendingo: Text replace - "" to ""

Icwiener: /* Custom fields */ typo

Icwiener: /* Custom fields */ typo

Icwiener: /* Hiding Fields */ typo

Milliams: No longer encessary. FindLibKDEGames.cmake is fixed

Milliams at 20:45, 28 April 2008

Milliams: /* Grouping Scores */

Milliams: Correct include path

Neverendingo: Text replace - "`" to ""`

`Neverendingo: Text replace - "`" to ""

Neverendingo: Text replace - "`" to ""`