[Kde-bindings] other issues with latest revision of smoke and korundum from 4.4 branch

Arno Rehn arno at arnorehn.de
Fri Jan 29 17:40:57 UTC 2010


On Friday 29 January 2010 12:08:06 Stefano Crocco wrote:
> Using the latest revision of smoke and korundum from the 4.4 branch, I've
> just found some possible bugs (everything worked correctly with smoke built
> with the old generator).
[snip]
Number 1 and 2 should be fixed now.

> 3) Maybe this is not an issue at all, but just the intended behaviour.
> However, it something which used to work and doesn't work anymore. The
> problem is that, given a KTextEditor::View which uses the kate part, I
> wanted to access the underlying KateViewInternal object (because I needed
> to install an event filter on it). With the old smoke version, the
> following worked perfectly (view is the KTextEditor::View returned by
> KTexEditor::Document#create_view):
> 
> view.findChildren(Qt::Object).find{|c| c.class == KateViewInternal}
> 
> With the new smoke, the above line gives a NameError
> (uninitialized constant KateViewInternal). I then tried to compare the
> class name rather than the class object itself. However, while it didn't
> produce any error, it returned nil. Trying to display the class of all
> children with Kate in their names I get:
> ["KateSpellCheckDialog", "KateBookmarks", "KateSpellingMenu",
> "KateLayoutCache", "KateWordCompletionView", "KateCompletionModel",
> "KateArgumentHintModel"]
> and no KateViewInternal. Given that KateViewInternal is, as the name
> states, an internal class, maybe leaving it out is intentional. I just
> wanted to be sure of this.
Yes. First of all, leaving it out would be intentional. But there isn't even a 
class named 'KateViewInternal' in any of the headers. If it has ever been 
there, it might have just silently disappeared. It's an internal class after 
all.
I hope you can find a way around it :).

-- 
Arno Rehn
arno at arnorehn.de



More information about the Kde-bindings mailing list