A good inspiration for that feature would be the Just My Code feature of recent visual studio : https://docs.microsoft.com/en-us/visualstudio/debugger/just-my-code?view=vs-2019
Best, Jean-Michaël On Mon, Feb 24, 2020 at 8:51 AM Shawn Rutledge <shawn.rutle...@qt.io> wrote: > > > On 22 Feb 2020, at 12:57, Ville Voutilainen <ville.voutilai...@gmail.com> > wrote: > > > > On Sat, 22 Feb 2020 at 13:07, André Pönitz <apoen...@t-online.de> wrote: > >>> Buy a debugger that can skip code that you didn't write. > >> > >> The point was that in a such a situation I, as user, would not even > >> try to step in when the call is marked with 'emit'. This 'emit' in > >> a line *is* valuable markup, that saves me time. > >> > >> That's unrelated to what the debugger would or could do if I did step > in, > >> I just don't need to follow that path. > >> > >> [And apart from that: There's no need to *buy* such debugger, e.g. gdb's > >> 'skip' actually works] > > > > It occurs to me that, in case Creator doesn't do that already, we could > make its > > debugger UI to automatically tell the underlying debugger to skip > > moc-generated code, > > as a default. > > I’m probably dreaming, but wouldn’t it be cool if it were possible somehow > to “step into” each handler function that is connected, while skipping over > the details of how we get there…. At least for direct connections. > > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development