View Single Post
Old 10-10-2018, 05:29 PM   #39
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,701
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
And that's just last year! But at least some portions of QFileIconProvider have to be working. Afterall... it's used to initialize the tree in the first place. All of the folder icons and the initial file icons are successfully retrieved via QFileIconProvider in OPFModel.cpp and Resource.cpp. It's only after reordering that things blow up in KDE

I believe QFileIconProvider has some flags that can be set to limit it to default icons only. I wonder if that's worth exploring?

Last edited by DiapDealer; 10-10-2018 at 05:35 PM.
DiapDealer is online now   Reply With Quote