Thanks, Bruce - I'll have a try at that. I did start the project with Qt4/5, but for some reason I now forget, I scrubbed it and changed to Gtk - seem to remember it had something to do with colours in some controls not appearing - and trying to get sound information about Qt or Gtk is like trying to thread spaghetti through the eye of a needle.

Big pity Benoit doesn't attend to reported bugs, in what is generally a very good environment. I can understand if he can't afford to get the kit to do it, if he's working on development alone or in a small group. (I don't know). Since he allows Gambas to be used almost as Open Source, perhaps he could throw it open to the 'community' to look at problems and help development work, and improve an otherwise good application. I've had lots of advice on using different languages and environments in the past, but I'm afraid that my opinion these days are that the vast majority of software development environments are, to coin a word, crap. For example, lots of drivel online about how good Python is, how easy it is to learn, etc, etc, but there is so much in the Python environment that is non-working, duplicated and/or obscure, that life is simply too short to bother - for example, a Mint installation sticks both Python 2 and 3 on your computer - more or less incompatible with each other. I have much the same opinion of things like Rust - great - its much more secure!  (probably because its so hard to use, no-one understands how to hack into it ! ).

What I would like to see is more effort to get existing tools to work better - I don't want to waste my time trying to learn a new language/environment from scratch every time I try to write an application - another reason I wanted to give Gambas a go - is there anyone in the coding world who doesn't know how to use BASIC (or its near equivalent)? - and I know all the arguments about the fallibility of BASIC - but most developers started on it, so why not improve it ? (As has been done with things like BBC Basic - still quite widely used).

Surely software is a tool, - a means to an end, like a screwdriver - but it only takes me a few seconds to learn how to use a screwdriver, and 'bugs' are obvious  - I only need to read back through this thread to see how long it takes to clarify the problems round what should be a simple procedure.

I know my opinions are not universal, but thats the way I feel. I used to love coding in what was then known as 'machine code' - native CPU instructions.  Ah well - I can dream.

All the best - An

Benoit is very active at fixing bugs.
Bugs he can reproduce.

And it's 100% open source.  Gambas / gambas · GitLab

If you think you can do a better job than Benoit then you are free to create a fork and fix all its problems you are finding.
<EMOJI seq="1f609" tseq="1f609">😉</EMOJI>

I have my own fork with many differences in the IDE to Benoits (and yours) version
Bruce Steers / gambas · GitLab
Check out the ReadMe for an incomplete list of my modifications  README.md · bruces-patched · Bruce Steers / gambas · GitLab

BTW I am not talking about running your project with GTK or QT , that makes no difference to the IDE.

I am talking about running the gambas IDE with QT

ANY project that uses gb.gui (including the gambas3 IDE) can be run the following ways from a terminal or via it's launcher command..
<HIGHLIGHT highlight="shell">

# Normally…
$ gambas3   # This runs the IDE with the desktops default toolkit.

$ env GB_GUI=gb.qt5 gambas3   # this will make the IDE try to use explicitly QT5 (not your project, you project will use what it is set to use)

# also this…
$ env GB_GUI=gb.gui.qt gambas3  # this will make the IDE use whatever QT your system has
</HIGHLIGHT>

Or If you right click your gambas3 launcher icon and select Properties (or edit your menu launcher) you can change the command.
change where it says
gambas3
to be this..
env GB_GUI=gb.gui.qt gambas3

then your IDE will use QT and you should not have the bug for Group editing.
This makes no difference to your project and the toolkit your project is set to use.

 Thanks again for the input, Bruce.

Sorry if I went off a bit in my ignorance - I was only offering an opinion based on what I have seen so far, and I sure don't want to criticize Benoit, yourself or anyone else for the good work.

I'll take a look at your advice, and you've opened up another lead to study (time permitting). Not always easy when you  find out about these things a long way down the line, as I am doing.

Regards, AN

 If you click on Group and write your group name then the text into field is hide or same color of background.
Then write in the field Group your group name and confirm with enter key. Then you can select your group in the combobox

 Thanks for that,rohtc.

I realised that after the  inputs I got earlier. I hope this thread makes it all a bit clearer fro other people like me, because there were some 'oddities' - such as the group entry not appearing. Simple answers, but not at all clear if not covered by the documentation, or discussed on a forum.

Regards, An