OK, thanks for the reply...
I will look to save i UTF-8, a little tiresome, but if that's the way to allow this to work, then so be it.. Can I assume that I can also use Unicode, direct?
This is an interesting problem. I have a .NET application that writes selections to a text file, and I do this using a list<string> variable, which I then write the file using a System.IO.File.WriteAllLines(filePath, list) method, and there is no overload option to use ANY encoding, which means it will more likely be in ANSI - yet, MFP reads these files OK, BUT, by setting an initial ANSI encoded file, MFP has problems with it... I honestly think you should fix that, because I have been experimenting, and the default setting for creating a notepad file and saving it, is ANSI, and, by creating a file in the default format, this created a problem with MFP. I expect most users will be using Windows OS?
As you are aware, if I need to add selections into a text file, MFP has a write to file action, and by leaving out my initial creation of this file, and allow MFP to take care of the writing, then what if I have another trigger that has a conditional to access that file, such as "selection's name is in file ...." - when I save the trigger, I will get a popup to ask me if I want to browse to the file, and of course, if I have to wait until a trigger writes the file, it becomes inconvenient. The ideal fix is that you change or update your code to inspect the encoding of the text file, and allow the appropriate reader/writer to do it's thing - having been a coder/software developer for many years, you have to establish most, if not all, user scenario's. This has clearly gone wrong, and the only action I took was to have a text file that I created, but MFP handled it incorrectly. I really would have expected MFP to be able to handle a text file that I created in my windows OS, using notepad as the creator of the text file. I can confirm to you that the default encoding in windows is ANSI
#### StreamReader(filename, true).CurrentEncoding ##### could be a possible option...? (You have to cater for BOM)
I know I am a very picky person, which is probably a nuisance to you, but I try to provide feedback, to help you improve the quality of your software - I am doing the stuff you haven't had time to do in your coding and subsequent testing/monitoring, hence my feedback.
As for the image problem...
When I create my post, I have the option to browse for an image.
AFTER I had posted my question, I then thought I should add in the placedFile image, for completeness. The only option available in the quick reply, is to add in a url link to the image - which I don't have. The file is located on my hard disk and not via a link. So, to be be able to post the image, I ended up dragging the image into the text area, and then clicked post. By doing that, the website throws an error to inform me that the text field cannot be more than 20,000 character (not sure if that number is correct - but it is along those lines) - once I get the error, I am then given a browse option, at which point, I can browse to the image and post it.
This is very simple to fix, you simply add in a link to the text area to allow the user to browse to locate an image.
It is not relevant whether any users have reported this, I have reported it, and I have shown you that there is no option to browse for the image, and yet, by purposely dragging the image into the text area, an error is thrown, after which point you have the option to browse. It would be much better if you provide the option to browse, but the original quick reply doesn't - that's what you need to fix it.