Parentheses "(" and ")" are lost when saving attachments

Technical support discussions and Bug Reports – You find em, we squash em
Marcel

Parentheses "(" and ")" are lost when saving attachments

Post by Marcel »

Example:
1. Attach a Word document with the name "Test (Version1).docx"
2. Click it with the right mouse-key and choose "Save as..."
3. Safe the document to the Windows desktop

→ The filename on the Windows desktop is now "Test Version1.docx".
It does not contain the parentheses any more.

But saving this file via drag&drop works correctly, without loosing this parentheses!

AllMyNotes 2.81 Portable, German, Windows 7 64bit.

Marcel.
vlad
Site Admin
Posts: 1132
Joined: January 6th, 2011, 2:58 pm
Location: Earth -> Europe
Contact:

Re: Parentheses "(" and ")" are lost when saving attachments

Post by vlad »

Indeed. Thank you for reporting this issue, it will be fixed in next app updates of version 2.xx and 3.xx (beta).
AllMyNotes Organizer usage tip: a free app for students to keep schedule, exercises, and homework
Marcel

Re: Parentheses "(" and ")" are lost when saving attachments

Post by Marcel »

This bug also causes the following:

1. Open a file (Excel-spreadsheet) that is attached to AMNO by double-clicking on it.
2. Make some changes
3. Close Excel and let Excel save the changes
4. → This attachment is not written back to AMNO.

This also happens to attached files that contain the following characters:
(
)
+
ß
ä
(maybe even more)


Marcel.
vlad
Site Admin
Posts: 1132
Joined: January 6th, 2011, 2:58 pm
Location: Earth -> Europe
Contact:

Re: Parentheses "(" and ")" are lost when saving attachments

Post by vlad »

Please try build 2.82 (the current one), it should be free from this problem. As for 3.xx version (beta), it will be fixed there too with next update.
AllMyNotes Organizer usage tip: a free app for students to keep schedule, exercises, and homework
Marcel

Re: Parentheses "(" and ")" are lost when saving attachments

Post by Marcel »

Since updating to AMNO 3.11 BEATA I can't reproduce the bug. It seems to be solved already.
Thanks for correcting this.
Post Reply