Similar to the ID-10-T error.

It sounds complicated but it's just using an "acrylic" Brush (available in UWP) instead of a regular "solid color brush" for the background. The same facility can be added to WPF using the "community tool kit". Or you can fake it varying the opacity of the background of a control ... though the "acrylic" brush seems to be a bit more "glassy". "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

At the end of the day the thing low code cannot do is "be a developer" I think. What happens in low code if you make, with its help, an error of intent instead of function? That is, "it worked as designed" but the design was wrong? When you have developers, you say "Oh, you guys got the design wrong. We meant ." (Kidding, mostly) You (as a developer) go do data-doctoring and maybe take care of some other adhoc processes that need to spin off and happen as a result of the issue. In low code? Do you just start pursuing creating those tasks in low code? How do you even know the need exists?

fgs1963 wrote: I know Steiner was into the occult but time travel was probably beyond his power. Oops - The 9 and 0 are next to each other. Latest Article: Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain

I'm so lazy that I defer even procrastination.

Watch this: Models - WPF MVVM TUTORIAL #1 - YouTube[^] - he will answer many questions for you, including this one! Graeme "I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee

You might consider whether .NET 7 is appropriate versus .NET 6. The pattern has generally been for every other .NET release to be an LTS (long-term service~3yrs) release versus an STS (~1.5yrs) release. .NET 7 will hit end of support May 14, 2024. .NET 6 will hit end of support November 12, 2024. Meanwhile, we should see an LTS of .NET 8 in November.

I sent him a warning. Thanks, Sean Ewington CodeProject

I doubt that has anything to do with it. Buying all those novels in paper form would cost well in excess of £100.

The AddOwner syntax lets you register another type for use with a DependencyProperty which has already been registered: How to: Add an Owner Type for a Dependency Property - WPF .NET Framework | Microsoft Learn[^] DependencyProperty.AddOwner Method (System.Windows) | Microsoft Learn[^] You can't use the TextDecorations class[^] as the property type; that's a static class used to provide access to the standard text decorations. Instead, you need to use the TextDecorationCollection class[^] as the property type, which is what the Inlines.TextDecorations property[^] does: Reference Source[^]: /// /// DependencyProperty for

Wheeler's Corollary to Hutber's Law: The gain from an enhancement will be offset by a greater deterioration, hidden by the enhancement. Software Zen: delete this;

{TemplateBinding x} should be equivalent to {Binding x, RelativeSource={RelativeSource TemplatedParent}}. The error is telling you that you can't set a RelativeSource on a TemplateBinding. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Thanks. I'll look into AWS If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.

Reported issue. They suggested running from console with DOTNET_TC_QuickJitForLoops=0 env var defined. That speeds it up slightly, although 6.0 is still a bit faster. I read somewhere that in 6.0, setting that to 0 speeds things up but that in .NET 7 there's no difference. Though to me it looks like it might be the other way round! So for 6.0 I get 0.53/0.54s (two successive runs). For 7.0 it is 0.57/0.58s. Still, nothing worth bothering about. Kevin

Kent Sharkey wrote: We're still good with .NET 1.1 though, right? It's still the preferred .net for NT4 applications. :-\ Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius