Home > .NET > FAQ

Why is the FAQ list so short?

The .NET version functionality, concept, and API are practically the same as in J2SE LwVCL version. See the J2SE LwVCL FAQ section. The other cause is that the version has just started its life, so we don't have a lot of questions to be published here.

I have noticed that the grid selection marker view has minor differences from J2SE version. Is it a bug?

The problem is that the .NET (v1.1) doesn't support the XOR mode for its graphical context. So we need to use another algorithm to render selection markers. The current .NET LwVCL version uses the color alpha component to make the selection marker transparent.

Is is possible to use the library for the MONO platform?

At the moment MONO doesn't provide an accomplished WinForms implementation. LwVCL doesn't need to have all WinForms features, we need only a small sub-set like basic UserControl, GC, Font ... classes. You can compile and probably successfully run the demo and samples applications under MONO. Pay attention that MONO compiler has some terrible bug: the virtual methods overriding can be lost if some intermediate class doesn't override a virtual method.

I cannot find LwToolkit and other classes in the "org.zaval.lw" package like J2SE LwVCL version. What is the new package for these classes?

.NET version uses the "org.zaval.port.cs" package for the following classes:

• The Java ported classes. These classes are analogues of appropriate classes from the Java class library (Graphics, Dimension, Rectangle, Insets, Hashtable, Enumeration, Color, Cursor, Font and many others).
  
  
• The LwVCL adaptive level classes. The classes are supposed to be re-implemented for concrete platforms and environments.

The LwToolkit class belongs to the adaptive level.