ecrire | Blog engine for developers | Blog library

You should set the center when the response is received. You may also want to zoom in:

You must not use fragile content, such as listings, as argument of other macros.

Anyway, the fbox\parbox is really superfluous - lstings has a frame option for this:

The index call will always return the first instance of the string. This is one of those situations where yor really want to loop over the indices of the list rather than directly loop over its elements.

Notice also that you can't del elements from the list you are currently traversing; but of course, when you loop over an indirect index, you can, as long as you termrnate on any IndexError.

This is a conceptual problem, you are trying to add event to a non-existing element… preventDefault() don’t help on this case. When working with dynamic elements creation, you need append events on element creation, like:

As mentioned by Jamie_D, using Location will forward the user to the specified address (like in your 3.3 Submission form code block).

Remove the line from your code block and you should get the desired download page:

The only problems your are facing are related to flushing your output streams. Because of that, even though the accept method passes succesfully the server side stays pending at the step of reading the input from the client.

Flushing makes sure that anything written to the writer prior to the call to flush() is written to the underlying stream, rather than sit in some internal buffer.

The method comes in handy in several types of circumstances:

• If another process (or thread) needs to examine the file while it's being written to, and it's important that the other process sees all the recent writes.

• If the writing process might crash, and it's important that no writes to the file get lost.

• If you're writing to the console, and need to make sure that every message is shown as soon as it's written

(See: How to use flush for PrintWriter)

I updated your code accordingly and it is working.

The updated server code:

You can't just place the button code in ReadData.cs class. as the event is related to ui of MainWindow.xaml create an object for ReadData do something like this

There are a few things I would do differently.

1/ Wrap your chat form in a tag, and execute the sendMessage() method on submit. This will give your users a nicer experience, as they can just to submit the message.

2/ Convert the button into a submit button so it triggers the form.submit event.

3/ You can easily disable the button by checking whether newMessage has contents. I don't think you need vee validate or anything else to achieve this; for something as simple as a chat form, your user doesn't need much more feedback than seeing a disabled button to realise (s)he needs to write something first.

4/ in the addMessage method you can just check the contents of newMessage and not do anything when it's empty. This is perfectly fine because you already hinted the user by disabling the button too.

I think this is a subtle way where you guide your user, but don't overdo it. Hope this helps.

This is how I would do it.
I would load the file as one string and use regex to parse the data.
Then I would loop one subarray and use the key in an array_column and array_combine to make it associative.