Hello
i use a memo in the server to brodcast the text to all clients (real time)
when i change on the memo, the socket should send the text to the clients then they clear the memo and update the memo with the new text
i put the sendtext on the event onchange in the memo.
the problem that when i change faster the client display multipile copies of the text and somehow randomly
but when i connect to 127.0.0.1 everything is ok.
by the way i dont use buffer , do i have to add it???
thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
OK, so you have to track when you memo is really changed...
Declare one more variable
var
MemoChanged : Boolean;
and you set some text - make it True and when you send - make sure it is True, send the text and make it false.
if the variable is False before sending - then don't send, because the memo was not changed...
you could try it the other way
start a timer evertime the onchange of the memo is invoked
if the user stops typing for about 200ms send the data to the other clients
if the onchange is invoked before the 200ms just reset the timer to zero.
so you dont need the sleep and 200ms after the user stopped flooding the memofield
with input the changes will be at the clients
regards
Business Accounts
Answer for Membership
by: ManiElanPosted on 2004-05-22 at 08:29:59ID: 11133364
An easy kill would be, keep a copy of the last send text and compare it with current one before send.