On Tue, Dec 8, 2020 at 10:49 AM Christian Kandeler
<christian.kande...@qt.io> wrote:
>
> > What where the arguments against a separate namespace field?
>
> Nested namespaces come to mind.

A separate namespace field could still support nested namespaces.
The issue I'm raising is simply that namespace support is hidden. Like
someone suggested in QTCREATORBUG-18965, a simple solution could be to
set a placeholder text like "Namespace::Class" to the class name
field.

But a separate namespace field would be preferable. Maybe label it
"namespace(s):" to indicate nested namespaces support, and add a note
that it is optional. A really nice feature would be to add an
auto-complete function to that field, or make it a combobox that is
populated with all namespaces from other files in the project.
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Reply via email to