The problem is that we have now already a lot of code without self. That's why I would at least prefer it if you could also switch on a warning
Hansjörg
Search found 24 matches
- Wed Feb 10, 2021 6:31 am
- Forum: Chit-Chat
- Topic: SELF: mandatory ?
- Replies: 8
- Views: 1966
- Fri Feb 05, 2021 6:01 am
- Forum: Deutsches Forum
- Topic: .Net Version
- Replies: 3
- Views: 1857
.Net Version
<t>Hallo,<br/> das ist nicht ganz korrekt so. NETStandard 1.1 und 2.0 sind zwar auch in .net Core benutzbar, allerdings auch gleichzeitig im .net Framework 4.x (je nach .net Standard Version ändert sich die Version). Erst der .net Standard 2.1 funktioniert außschließlich mit .net core. Falls eine Li...
- Wed Nov 18, 2020 8:07 am
- Forum: Examples
- Topic: WPF versus Winforms: how to get a decent directory selection option
- Replies: 14
- Views: 5047
WPF versus Winforms: how to get a decent directory selection option
<r>Hi Dick,<br/> you can use the Ookii.Dialogs.Wpf (<URL url="https://github.com/augustoproiete/ookii-dialogs-wpf">https://github.com/augustoproiete/ookii-dialogs-wpf</URL> -> <URL url="https://www.nuget.org/packages/Ookii.Dialogs/">https://www.nuget.org/packages/Ookii.Dialogs/</URL>)<br/> Hansjörg<...
- Wed Nov 11, 2020 1:22 pm
- Forum: Product
- Topic: Constant redefinition warnings RX4005 when working in VO Windows-Editor
- Replies: 28
- Views: 4317
Constant redefinition warnings RX4005 when working in VO Windows-Editor
<t>At the moment the VOXPorter defines the values as int. It is read in the array of xPorter.SDKDefines[cUpper] as string. In theory it is possible to convert it to a int64 and format it as a hexstring in Generate_Resources in the following case<br/> <br/> CASE xPorter.SDKDefines:ContainsKey(cUpper)...