Fixing 49564 - dependency/BC problem?
staikos at kde.org
Sun Mar 9 01:27:59 GMT 2003
There is a virtual_hook there that you can use to add a virtual function
without breaking BC.
On Saturday 08 March 2003 19:55, Ravikiran Rajagopal wrote:
> KConfigBackEnd::sync() returns nothing, and hence fails silently when the
> user's local config file is not writable. As I understand it, we cannot
> have kdecore dependent on kdeui. So we cannot use a UI element to make the
> user aware of the situation.
> The only alternatives I can think of:
> 1. Add a sync() function which indicates success or failure - not possible
> to due to BC issues as sync() is virtual. Don't know whether changing a
> return type is BC though.
> 2. Emit a signal saying it failed, and let the app take care of it. Does
> not help existing binaries, and _all_ apps need to be ported.
> 3. Add a function canWeSaveConfig(). This has the same problem as #2.
> 4. If the user's local config file is not writable, try to make it
> writable. Very invasive, and I don't like it.
> Should I mark this bug as WONTFIX due to BC issues? If we do make a change
> and #1 is ruled out, my inclination would be for #4. Why would someone
> outside of the kiosk mode make use of read-only config files?
More information about the kde-core-devel