Quote Originally Posted by Nyphel View Post
Yes, great idea

Link to the project archived in ZIP format
Link to the project archived in RAR format
Khyym... please use the attachment feature of the forum next time. We don't like external links here.

I should have taken a MVC approach, yes, but this project was just a small personnal project in order to list me what movies I have on my computer. I made the first build very simply, and I didn't took care about the conceptual approach... Shame on me !
That's the reason why I didn't read all the informations relative to QTreeWidget in the Qt Assistant, and didn't saw the View and Model aspects avaibled for this widget .
That's usually the problem. You start with something simple and suddenly it happens to be a big project. You're wasting much effort operating on the filesystem and you could have just used QDirModel with an optional proxy model to filter out entries you didn't want. You should think about redesigning it...


EDIT : I've not really backtraces or debugger under the hand.
I simply displays some comments on the cout at each step, in order to detect and target where the application crashes.
That's not good, because what's important is not only that where the application crashes but also which method invoked the method that crashed and with what parameters. Unless you provide us with something small and compilable, you have to provide the backtrace yourself. Currently there's just too much code to analyse. It could be that the crash is caused by one of the threads (from what I understand you are using threads). Don't you by any chance operate on the tree from within a worker thread? Anyway please provide the backtrace or cut down the project to something small that reproduces the problem.