Full .NET port of GUI

[GoogleCodeExporter]

When will this be done and should I just give it a CBFD right away?

What needs to be done:
 - DirectInput with C# / C / C++
        I have already looked into this and it seems that is a 500+ line of code job just to get the joystick to work.  If you can find a simpler way that would be great.
 - GUI with multiple WinForms.
 - Other stuff, like TCP client, etc.

Original issue reported on code.google.com by cian.by...@sydstu.catholic.edu.au on 9 Mar 2013 at 12:14

[GoogleCodeExporter]

I read on the homepage and remember a build like this has been made for Windows 
8.  Can you find the source code for this please and publish for review by me.

Original comment by cian.by...@sydstu.catholic.edu.au on 11 Mar 2013 at 2:57

[GoogleCodeExporter]

I am not impressed with my communication skills at the moment.  Anyway,  It is 
now day time and I can communicate with you here.  From what I can see that was 
done @0300 this morning, we need to communicate our ideas and come to a 
compromise.

Currently:

 - Form1 has all the preferences like in the XAML file
 - Form1 has all TCP Client code (not correct)
 - Form2 (named: Joystick_TCP.vb) has nothing except for minor joystick tools
 - Form# (named: ClientForm) only has GUI elements code ???  I feel like just deleting it.
 - Form TCPmodule.vb has code that is all commented out.  I feel like deleting this one too.

Anyway,  This is how I believe the program should be executed:

Pre-Steps: orm

Loads Form1
Input all preferences [User ticks boxes, etc]
Then it gets complicated: PRESS START!! --> Show.Form2()

1. On load of Form2 (Joystick_TCP), Form2 will get the variables from form1.  
This will pass them as the following:
    _TCPEn
   _JoystickEn
   _DebugEn
   _HOST
   _PORT
   _CMDrobot

The first ones in the list are all 'y' or 'n' values

2. On Load of Form2, TCP Should attempt connection if TCP mode is enabled

2a. This connection should either:
 i. Connect and wait for data to be sent
ii. Not Connect and alert User that it has not connected.

The way that these should be executed is maybe load another Form called 
TCPClient Which onload should automatically attempt connection one. (JUST LIKE 
IN PYTHON).  If Connection One fails, the box will stay there with reconnect 
buttons, two labels, two textboxes. "RECONNECT" button, and the two textboxes 
which allow for address to be changed.

I will do up a draft of this now.

After we have sorted out the TCP seems to be the most complicated side of 
things, then I can move onto a straight port from Control Module Beta 1.6.6 to 
.NET.

Please sort out TCP Client using the variables: 
 _TCPEn
 _PORT
 _HOST

Try not to mess around with my code too much.  Also Try to create a 
class/function for sending data.  Then we can just call that class/function 
when we need to (and also I'll know how to do it.)

Original comment by cian.by...@sydstu.catholic.edu.au on 15 Mar 2013 at 11:45

• Changed state: Started

[GoogleCodeExporter]

Attached.

Original comment by cian.by...@sydstu.catholic.edu.au on 16 Mar 2013 at 12:24

Attachments:

• JoystickTesting_.NETport.rar

[GoogleCodeExporter]

I am unable to decode your VB code.

It is up to you to move your TCP Client into the 'Joystick_TCP.vb' file.

Make sure you DO NOT use any buttons to start functions.

ONLY USE BUTTONS TO CALL OTHER FUNCTIONS NOT TO BE THE FUNCTION.

Please make two Functions:
 - sendtoserver()
 - connecttoserver()

Original comment by cian.by...@sydstu.catholic.edu.au on 16 Mar 2013 at 1:24

[GoogleCodeExporter]

Attached is the not work version of the TCP Client.

I expect it to be working within the next 3 hours.

Original comment by cian.by...@sydstu.catholic.edu.au on 16 Mar 2013 at 1:51

Attachments:

• JoystickTesting_.NETport-TCPdead.zip

[GoogleCodeExporter]

We are almost done!  I have uploaded the latest version to the dl page.

Can you:

 - Strip out all the old and redundant \TCP folder and files.
 - Make GUI look 10 times better.
 - Make it so that you can see what each motor's speed is in km/h (so for you: make two nice txtboxes so that I can manipulate the data inside of them)
 - Remove all the extra buttons or give them something to do.

I might work on it on Tuesday or Monday in Study Period if I get time.

Over to you...

Original comment by cian.by...@sydstu.catholic.edu.au on 16 Mar 2013 at 1:27

[GoogleCodeExporter]

Team Foundation server is online!  and the project has been sync-ed!!

Changed Priority: 

Original comment by cian.by...@sydstu.catholic.edu.au on 18 Mar 2013 at 11:25

• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

.NET port is almost complete...

- only GUI and colours need to be fixed.

Original comment by cian.by...@sydstu.catholic.edu.au on 24 Mar 2013 at 9:19

[GoogleCodeExporter]

Almost complete... We are up to the part where you need to make it 
aesthetically pleasing (Tom).

Advice: 
 - Remove as many buttons as possible from the 'Form1'
 - add to the tab system that I have put down in the 'JoyTCP'
 - COLOURS

Original comment by cian.by...@sydstu.catholic.edu.au on 27 Mar 2013 at 10:33

[GoogleCodeExporter]

Process complete, adding more features!

Original comment by cmdenterpriseshq on 6 Apr 2013 at 1:28

• Changed state: Done

[GoogleCodeExporter]

Do you have current version?  Make sure you keep checking-in and checking-out 
so that we have a backup on Server2012.

Original comment by cian.by...@sydstu.catholic.edu.au on 7 Apr 2013 at 3:37