clayborg added a comment. In D97739#2596218 <https://reviews.llvm.org/D97739#2596218>, @jingham wrote:
> I haven't thought about the details of this implementation closely yet. How > will this handled nested progress bars? For instance, if I'm Indexing (maybe > even on multiple threads) and then one of the threads results in a debug > symbols fetch request (e.g. dsymForUUID). Is the consumer just supposed to > check the string that comes into the progress callback to match the now two > simultaneous progress elements? Nesting doesn't matter. I am in the process of adding a "uint64_t progress_id;" to each progress class that will be included in the callback. This will allow as many progress activities to be created from as many threads as needed. All activities will show up as top level activities. So the user will use the "uint64_t progress_id" as the unique indicator. This allows the same message to be used for multiple different progress indicators to avoid potential conflict if the user uses too simple of a string. I am about to post an update. Check the Progress.h header doc once I update this patch, hopefully this will answer any questions you might have. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D97739/new/ https://reviews.llvm.org/D97739 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
