Plugins depending on the standardoutputview with no Ui

[Dmitry Risenberg]

2011/3/23 Julian Bäume <julian at svg4all.de>:
> Am Mittwoch, 23. März 2011, 11:51:34 schrieb Dmitry Risenberg:
>> 2011/3/23 Andreas Pakulat <apaku at gmx.de>:
>> > On 23.03.11 11:18:18, Julian Bäume wrote:
>> >> Hi,
>> >>
>> >> Am Mittwoch, 23. März 2011, 09:45:22 schrieb Andreas Pakulat:
>> >> > PS: The KDevPlatform codebase has not been written with non-gui apps
>> >> > in mind, hence you can always run into code-paths where suddenly ui
>> >> > is needed. As the no-ui mode usually is used without KApplication or
>> >> > at least without X11 connection, that means your app will crash at
>> >> > that point.
>> >>
>> >> What’s the use for KDevelop::Core::NoUi then?
>> >
>> > To get kdevplatform loaded into an app that uses KApplication without X11
>> > connection (or QCoreApplication+KComponentData as the tests do). That
>> > however is a hack and you've to be rather careful what you do with the
>> > kdevplatform libs as not all code-paths have been tested or examined for
>> > necessity of this flag to disable certain things. In particular when
>> > errors occur the code may still try to show message-boxes or what-not to
>> > the user.
>>
>> Can I check this flag to avoid showing a messagebox when code is
>> called from a no-gui test suite?
>
> No, the plugins just won’t load, when they need the GUI and you set the NoUi
> flag.

The code itself is in kdevplatform (itemrepository.cpp), it does not
need GUI, but it shows a messagebox in case of an error, which causes
a crash when run from unit tests, so I think that checking for NoUi
flag will fix it, won't it?

-- 
Dmitry Risenberg