[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 128307] New: Starting a second instance of applet from
From:       Daniel <dd () accentsolution ! com>
Date:       2006-05-30 8:31:31
Message-ID: 20060530103127.128307.dd () accentsolution ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=128307         
           Summary: Starting a second instance of applet from SuperKaramba
                    insterface starts broken applets
           Product: superkaramba
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: p0z3r earthlink net
        ReportedBy: dd accentsolution com


Version:           0.39 (using KDE KDE 3.5.2)
Installed from:    SuSE RPMs

Hello Ryan.

Starting a second instance of applet from SuperKaramba insterface starts broken \
applets. By broken I mean they seem to be lost about where to load all the images \
from. As a result, a new blank area appears on the desktop and the following shows up \
in console:

sys.path.insert(0, '/home/dd/musor/projects/afoto/afoto-1.5b-3.skz')
Call to initWidget failed
Traceback (most recent call last):
  File "/home/dd/musor/projects/afoto/afoto-1.5b-3.skz/afoto.py", line 512, in \
initWidget  File "/home/dd/musor/projects/afoto/afoto-1.5b-3.skz/afoto.py", line 336, \
                in loadTema
ValueError: widget does not have meter 825b700.

Starting a second instance of the same applet by means of double-clicking the SKZ \
file itself, reliably starts additional applet instances.

(You are probably asking yourself, "Why in the world anyone needs more than one \
instance of an applet?" :) )

By the way, while we are at it... Is there any way for superkaramba to remember the \
order of closing of multi-instance applets? It seems the 1st setting ever created \
will be used 1st. (FIFO) I would probably prefer it to be "the last applet setting \
used" will be used 1st on superkaramba reload. (LIFO) Ideas? If too much hustle, I'll \
just implement inter-applet communication over sockets, or something... So they can \
figure out which setting was used last themselves.

Happy bug hunting!


[prev in list] [next in list] [prev in thread] [next in thread]