Bug 172929 - kolf: It's unreasonably difficult to edit levels
Summary: kolf: It's unreasonably difficult to edit levels
Status: CONFIRMED
Alias: None
Product: kolf
Classification: Applications
Component: general (show other bugs)
Version: 1.9
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-16 10:22 UTC by Mark Purcell
Modified: 2021-03-11 01:23 UTC (History)
2 users (show)

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 Mark Purcell 2008-10-16 10:22:31 UTC
Version:           1.9 (using 4.1.2 (KDE 4.1.2), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-1-686

Forwarded: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491250

From: Russell Coker <russell@coker.com.au>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kolf: It's unreasonably difficult to edit levels
Date: Fri, 18 Jul 2008 10:02:43 +1000

Package: kolf
Version: 4:3.5.9-2+b1
Severity: normal

To edit a level I first have to start a game.  That makes no sense.

Then if I want to create a new level I can't just select that menu option, I
first have to edit a level.  So I have to select to edit a level that I don't 
want to change in order to be able to create a new level.

The kgoldrunner game has a good system for editing levels (including a slider
for selecting which level in a game to edit and previews).

Maybe it would be possible to create a kde library for managing the process
of loading and saving levels.  If not a straight copy/paste of code from
kgoldrunner would improve things.


I believe that a young child should be able to edit levels without assistance.
This is possible with kgoldrunner but not with kolf.
Comment 1 Stefan Majewsky 2011-05-30 23:50:44 UTC
Confirmed.
Comment 2 Justin Zobel 2021-03-11 01:23:56 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.