Topic: VB.NET to C#

[pkohut]

in that case, how about

Code: [Select]

if(Convert.ToBoolean(e.Context.History & PointHistoryBits.NotDigitizer))

Hm, heard something about boats and floating...

[It's Alive!]

in that case, how about

Code: [Select]

if(Convert.ToBoolean(e.Context.History & PointHistoryBits.NotDigitizer))

Hm, heard something about boats and floating...

eh ?    just throwing out alternatives

[gile]

in that case, how about

Code: [Select]

if(Convert.ToBoolean(e.Context.History & PointHistoryBits.NotDigitizer))

This seems to be closer to the VB syntax. It seems to me, VB can have non explcit casts.

[It's Alive!]

It's just C# is a bit more "type safe" than other languages, I wonder what refector shows in this case...

[pkohut]

eh ?    just throwing out alternatives

Understood. The humor must of stopped at keyboard 

[It's Alive!]

Yeah, I better go get myself a few happy pills BRB 

[It's Alive!]

Ok chugged a redbull... where was I   

[Kerry]

That should teach me about not testing before posting.  

[sinc]

Now as per the suggestions given yesterday, if I use

 if(args.Context.History & PointHistoryBits.NotDigitizer == 2)

compiler says that we cannot compare int with PointHistoryBits.NotDigitizer, so even this version is not working.

That's because of operator precedence.  You would need to do something like the following:

Code: [Select]

if ((args.Context.History & PointHistoryBits.NotDigitizer) == 2)
Without explicit parentheses, it gets parsed as:

Code: [Select]

if (args.Context.History & (PointHistoryBits.NotDigitizer == 2))

[gile]

After some tests:

((args.Context.History & PointHistoryBits.NotDigitizer) == 2) => does not work

((e.Context.History & PointHistoryBits.NotDigitizer) > 0) => does not work

((e.Context.History & PointHistoryBits.NotDigitizer) != 0)) => works

(((int)e.Context.History & (int)PointHistoryBits.NotDigitizer) == 2) => works

(((int)e.Context.History & 2) == 2) => works

((e.Context.History & PointHistoryBits.NotDigitizer) == PointHistoryBits.NotDigitizer) => works

((e.Context.History & PointHistoryBits.NotDigitizer) > PointHistoryBits.DidNotPick) => works

(Convert.ToBoolean(e.Context.History & PointHistoryBits.NotDigitizer)) => works

[Kerry]

Just to confuse the iisue more,
The VB code as written is massaged behind the scenes and the decision logic is changed ... one of the reasons ( no, we won't go there today )

This is the VB code

Code: [Select]

   ' ok, so now lets do something really pointless! space invaders!
    If (e.Context.History And PointHistoryBits.NotDigitizer) Then
      ' this means the mouse has been clicked... so...
      ' create a Circle
      Dim circle As Circle = New Circle(e.Context.RawPoint, Vector3d.ZAxis, 10)
      ' draw it
      e.Context.DrawContext.Geometry.Draw(circle)
      ' wait for a while
      System.Threading.Thread.Sleep(50)
      ' draw it
      circle.Radius = 20
      e.Context.DrawContext.Geometry.Draw(circle)
      ' wait for a while
      System.Threading.Thread.Sleep(50)
      ' draw it
      circle.Radius = 40
      e.Context.DrawContext.Geometry.Draw(circle)
      ' wait for a while
      System.Threading.Thread.Sleep(50)
      ' draw it
      circle.Radius = 80
      e.Context.DrawContext.Geometry.Draw(circle)
      ' wait for a while
      System.Threading.Thread.Sleep(50)

    End If
These are snaphots into the compiled code in Reflector // both the VB and C# representation of the Intermediate Langusge in the compiled DLL
note : the piccys will only be visible to members logged-in.

[jgr]

This code is not correct because it only works if Option Strict = off. (this is a compiler option)

Code: [Select]

If (e.Context.History And PointHistoryBits.NotDigitizer) Then
This is the right way.

Code: [Select]

If (e.Context.History And PointHistoryBits.NotDigitizer) = PointHistoryBits.NotDigitizer Then

This also works

Code: [Select]

If (CInt(e.Context.History) And Cint(PointHistoryBits.NotDigitizer)) = 64 Then

If (CInt(e.Context.History) And 64) = 64 Then

If CBool(e.Context.History And PointHistoryBits.NotDigitizer) Then

...

[Kerry]

This code is not correct because it only works if Option Strict = off. (this is a compiler option)
< .. >

That statement is debatable.
Option Strict = off is an available Option .. so the code is correct in the form it's used.

The real discussion should be "why is Option Strict available as an Option, and should it be used at all"
.. but I won't participate 'cause I'm prejudiced 

.. just my opinion

 

[jgr]

Option Strict = off is an available Option .. so the code is correct in the form it's used.

The real discussion should be "why is Option Strict available as an Option, and should it be used at all"

It is an inheritance from vb6. This option does not exist in vb6 but internally is always off.

Option Strict On provides strong typing.
http://msdn.microsoft.com/en-us/library/zcd4xwzs%28v=VS.100%29.aspx