Bug 150363 - game type not displayed after restart
Summary: game type not displayed after restart
Status: RESOLVED FIXED
Alias: None
Product: knetwalk
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Fela Winkelmolen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-30 23:49 UTC by Jo Schulze
Modified: 2008-06-24 19:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jo Schulze 2007-09-30 23:49:36 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

The current game type isn't displayed in the Setting menu when starting knetwalk (there are no checkboxes in the Settings -> Choose Game Type submenu).
This makes it hard/impossible so differ wether you are in Expert or Master mode.
Comment 1 Burkhard Lück 2007-10-10 23:07:25 UTC
I confirm this bug for trunk/kdegames/knetwalk r723832

On the first start of knetwalk no Difficulty ("Easy" etc) is selected in
the dropdown box in the right bottom corner of the main window nor in the menu Settings->Difficulty
Comment 2 Fela Winkelmolen 2007-10-21 23:32:31 UTC
SVN commit 727830 by fela:

* Renamed the difficulty levels in the config file to use the KGameDifficulty names.
* Bugfix: the default difficulty level wasn't working, consequently when starting the program for 
the fist time there was no current difficulty shown.
BUG:150363


 M  +0 -1      cell.cpp  
 M  +6 -6      knetwalk.kcfg  
 M  +8 -8      main.cpp  
 M  +10 -3     mainwindow.cpp  
 M  +0 -1      mainwindow.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=727830
Comment 3 Olivier Vitrat 2008-02-24 23:15:27 UTC
this is not fixed in 3.5.8 ...
Comment 4 Jo Schulze 2008-02-25 01:05:21 UTC
Neither in 3.5.9
Comment 5 Ana Guerrero 2008-06-24 18:37:35 UTC
It looks like the fix was commited only to KDE 4.
Comment 6 Fela Winkelmolen 2008-06-24 19:00:11 UTC
Yes, the bug wasn't easily backportable. I'm considering bugs fixes in kde 4.* as fixed.