Ok, I guess I need to read the docs on a class BEFORE just assuming that it'd work the way other Qt/KDE classes work.... Case and point KListViewSearchLineWidget (say that ten times fast, I dare you...)
Unlike most classes in KDE which take the parent as the first entry, it takes the KListView that the search will be tied to. This is, in my opinion, the epitome of inconsistent code design :( After spending two days getting that widget to display and run properly, I finally broke down and read the documentation.
Yeah, yeah... I should have read the fine manual earlier, but I had gotten lulled into a false sense of thinking that "this is KDE code, it'll be logical with how it handles constructing the object and it will be consistent". This learns me one....
Whoever designed Swing must have snuck that in there. ;)
ReplyDelete