xsharp.eu

Strangely, i never used the background property of SLE...
- now i want to change it and fail at securing the "old" Background prior to any action.

On a Vo-style datawindow, in my sle class' constructor, i added a
SELF:oOldBrush:= SELF:Background
Debugging, i get SELF:Background is NULL - why?

Hi Karl,

I think that means that there's no specific color used, VO just allows the OS to draw the control with the default color.

Yes, the background brush is only set when a non standard background is set by the program. Otherwise the standard functionality is used. If the Windows XP Themes are enabled, brushes are seldomly used because they cannot interfere correctly with the complex Theme rendering. In previous times (Theme support not enabled) brushes were useable much more.

Arne

Chris, Arne,
thx for explaining. Indeed it works backwards, too, ie, a background set by the designer dissappears, when the property is set to Null.

Another pit i stumbled into was this:
SELF:oBG :=Brush{Colorred}
which produced neither warning nor error. After some thinking, i now understand: a define internally is a number, which suffices as a usual

Time to advance finally to the typed gui classes - i take it, these would throw here an error?

A related question:

Is it possible to give the SLE's on VO-forms rounded corners in Windows 10, like they have automatically in Windows 11? Our clients like the rounded corners very much, but they also prefer Windows 10 over Windows 11.

Kees.

Hi Kees,
Windows 10 goes out of maintenance in about a year, so your clients should upgrade.
Wolfgang

Hi Karl,
the typed GUI classes are a lot better, but be prepared to some side effects because of strong typing.
And currently there is no bBrowser for them.
Wolfgang

Yes, technically it is possible to have the round corners, but it may cost so much that the customer surely will not want to pay for it.

Now we use the expensive Devexpress controls library together with Winforms windows and the design of the controls is now with round corners. The devexpress library makes its own rendering which costs also additional time to show the whole windows. There may be also some other libraries that make some "Scinning".

I would recommend to speak about security with the customer.
According to the statistics it seems much more safe to use Win 11 instead of Win 10.
From October 2025 Win 10 will not receive normal updates anymore.
Of course unfortunately there may be heavy hints: Many PCs cannot be converted to Win 11. So it is worth to make already some plans about Autumn next year.

So it is time to begin to convert the PCs where possible and to use Win 11 with all new PCs.

In our company we also have still more Win 10-PCs than Win 11-PCs. But the move to Win 11 has started.

Arne

Hi Arne,
one thing about PCs not more compatible with Windows 11: they are at least 7 years old, so they have done their service for business use.
Wolfgang

Hi Wolfgang,

in my eyes many PCs are still useable for work, as much of the heavy calculation work resides on servers. So this should not be the point of decision.

I still ask me if the Microsoft decisions were really only security reasons, same with the coming "IA-Chips".

But we are forced to follow what Microsoft decides and we must be glad that we make programs for such a successful operating system.

Arne