Main Page   Modules   Namespace List   Class Hierarchy   Compound List   File List   Namespace Members   Compound Members   Related Pages  

KSimpleConfig Class Reference

KDE Configuration Management class with deletion ability. More...

#include <ksimpleconfig.h>

Inheritance diagram for KSimpleConfig:

KConfig KConfigBase List of all members.

Public Methods

 KSimpleConfig (const QString &fileName, bool bReadOnly=false)
virtual ~KSimpleConfig ()
virtual void sync ()

Protected Methods

virtual void virtual_hook (int id, void *data)

Detailed Description

KDE Configuration Management class with deletion ability.

KDE Configuration entries

This is a trivial extension of KConfig for applications that need only one configuration file and no default system. A difference with KConfig is that when the data in memory is written back it is not merged with what is on disk. Whatever is in memory simply replaces what is on disk entirely.

Author:
Kalle Dalheimer <kalle@kde.org>, Preston Brown <pbrown@kde.org>
Version:
Id:
ksimpleconfig.h,v 1.24 2002/03/03 21:20:26 lunakl Exp
See also:
KConfigBase KConfig

Definition at line 43 of file ksimpleconfig.h.


Constructor & Destructor Documentation

KSimpleConfig::KSimpleConfig const QString &    fileName,
bool    bReadOnly = false
 

Construct a KSimpleConfig object and make it either read-write or read-only.

Parameters:
pFileName  The file used for saving the config data. Either a full path can be specified or just the filename. If only a filename is specified, the default directory for "config" files is used.
bReadOnly  Whether the object should be read-only.

virtual KSimpleConfig::~KSimpleConfig   [virtual]
 

Destructor.

Writes back any dirty configuration entries.


Member Function Documentation

virtual void KSimpleConfig::sync   [virtual]
 

Flushes all changes that currently reside only in memory back to disk / permanent storage. Dirty configuration entries are written to the most specific file available.

Asks the back end to flush out all pending writes, and then calls rollback(). No changes are made if the object has readOnly status.

You should call this from your destructor in derivative classes.

See also:
rollback(), isReadOnly()

Reimplemented from KConfigBase.


The documentation for this class was generated from the following file:
Generated on Wed Aug 13 23:30:24 2003 for kdelibs by doxygen1.2.18