"dlglib" Radiobutton loses Disabled or Invisible attribute.

[circe]

If two or more Radiobuttons are are in the same group, and one is Disabled (WS_DISABLED) or Invisible (WS_VISIBLE), then that button loses its attribute if another button is selected.

To demonstrate this, load DLGDEMO.BBC from @lib$,
Change the Style of Radiobutton 2 from 0 to WS_VISIBLE (or WS_DISABLED)
Run the program, and click on Radiobutton 1 (even though it is already selected).

Radiobutton 2 will lose it's Grey or Invisible appearance even though it may still not be selected.
Purely a visual problem, unless there are other implications that I have not found (yet).

[Richard Russell]

If two or more Radiobuttons are are in the same group, and one is Disabled (WS_DISABLED) or Invisible (WS_VISIBLE), then that button loses its attribute if another button is selected.

I can't say that I've ever considered the possibility of disabling (or hiding) a subset of a group of Radio Buttons, nor can I recall ever using an application with that behaviour. Is it something that you can legitimately do with native Windows controls?

If you want to suggest a modification to dlglib.bbc which would implement that feature I would be happy to consider adding it to the released version in a future update.

[circe]

In my view, it is not a request for a new feature, but to make an existing one work as expected and as I recall, they did in BB4W.
Certain facilities could be made available conditional on other factors.
But I do not consider it urgent as the effect is only visual. Next release sounds good.

[Richard Russell]

In my view, it is not a request for a new feature, but to make an existing one work as expected and as I recall, they did in BB4W.

There should be no 'expectation' that BBCSDL's UI widgets will work "as they did in BB4W". There is not the slightest chance that they will, because the code for the native Windows controls used by BB4W was written by a large team of UI and coding experts at Microsoft over a period of several decades. The code for the BBCSDL controls was written, mostly by me, in BASIC, in a few days!

BBCSDL's controls are therefore inevitably primitive, both graphically and functionally, compared with native Windows controls, and any request for a functionality they don't already have is a request for a new feature. Not only that, but because of my poor cognitive health it's unlikely that I would be able to write the code to achieve it.

If you are not concerned about portability to other platforms there is no reason why you shouldn't use native Windows controls (in BB4W, or even in BBCSDL, in principle). Quite some time ago I made a request for somebody (or a group of users) to write a set of 'WINLIB' style libraries for BBCSDL which would reproduce some of the functionality of the equivalent BB4W libraries. Unfortunately there were no volunteers.

However I am not the only one who has (or more accurately once had) appropriate expertise: the BBCSDL Tree View control was written by Svein and is quite complex in its own right, and the entire BBCEdit IDE was written by Andy Parkes. So there is still hope that new features can be added, just most likely not by me.

[Richard Russell]

But I do not consider it urgent as the effect is only visual. Next release sounds good.

You need to keep searching for a bug so serious that it will require another release sooner rather than later.

Meanwhile I do from time-to-time update the GitHub Repository without it triggering a new release, so you may on occasion find an updated library or new example program there.