Timeline for Using delegates to communicate between forms and networkcommunicator class
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2015 at 2:21 | history | edited | Quill | CC BY-SA 3.0 |
added 4 characters in body
|
| Oct 15, 2014 at 14:29 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 354 characters in body
|
| Sep 29, 2013 at 15:37 | vote | accept | Cyberbird | ||
| Jan 1, 2013 at 14:49 | history | edited | svick | CC BY-SA 3.0 |
rm tag from title
|
| Dec 31, 2012 at 13:47 | comment | added | Cyberbird | Well since it's part of my thesis, i can't do that right now, but after February I don't see a problem doing it. | |
| Dec 31, 2012 at 12:16 | comment | added | CodeTherapist | I d'like to join an open source/freeware project soon. If you wish, upload it to codeplex and we can work on it :) | |
| Dec 31, 2012 at 11:15 | comment | added | Cyberbird | You could say that, it's not distributed anywhere. i'm perparing for my bsc thesis, and this is a proof of concept, that a free implementation of a pretty expensive program can be done, in a relatively small amount of time. Since I'm more of a network engineer, i feel I'm a bit in over my head here, hence my above question. Also after February(hopefully) the source code will be made available on some public source control site. | |
| Dec 31, 2012 at 11:08 | comment | added | CodeTherapist | Is this a freeware/opensource project? | |
| Dec 31, 2012 at 11:08 | answer | added | CodeTherapist | timeline score: 1 | |
| Dec 31, 2012 at 10:28 | comment | added | Cyberbird | Well, for the LoginForm it's not entirely necessary, however, other forms work in a manner that they need it. What the server does is, it connects to a device via serial port, and sends everything the device writes there, to the client, and writes everything to the device which the client sends using a basic protocol WRITE_DEVICE|DEVICE_ID|MESSAGE. So because of this, at least some of the client's forms have to work async. Because they have to show the message, the device sends while being able to send messages themselves. Also there could be multiple devices, which i handle on tabbed forms. | |
| Dec 30, 2012 at 23:17 | comment | added | Leonid |
Does the communication need to be truly asynchronous? The LoginForm does not need it. It should spin around and wait until the login succeeds. What about the other form? Give me an example of the type of communication that goes on.
|
|
| Dec 30, 2012 at 21:19 | comment | added | Cyberbird | Forms send their messages to the server only (through one tcp connection) using delegates however each form can receive message from the server. I Think your idea about the MainForm vs Loginform is quite right, i don't know why i didn't do it that way. | |
| Dec 30, 2012 at 20:30 | comment | added | Leonid |
Feel more complex than it should have been. Is it a two-way communication, or do forms send their message in one direction only? Also, I believe that the MainForm should temporarily show the LoginForm, and not what you have - a LoginForm permanently shows the MainForm. I would simplify things as much as possible first.
|
|
| Dec 29, 2012 at 21:59 | history | edited | Cyberbird | CC BY-SA 3.0 |
added 20 characters in body
|
| Dec 29, 2012 at 18:10 | history | edited | Cyberbird | CC BY-SA 3.0 |
edited title
|
| Dec 29, 2012 at 17:44 | review | First posts | |||
| Dec 30, 2012 at 8:15 | |||||
| Dec 29, 2012 at 17:35 | history | edited | Cyberbird | CC BY-SA 3.0 |
grammar
|
| Dec 29, 2012 at 17:24 | history | asked | Cyberbird | CC BY-SA 3.0 |