[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-08-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

--- Comment #9 from giovani  ---
Sorry, but I didn't know if I should send here or in the other topic so I sent
in both.

https://bugs.documentfoundation.org/show_bug.cgi?id=156499

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-08-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

--- Comment #8 from giovani  ---
Hi guys!

Thanks you all the feedback about this subject.

I think the main problem in my case is that in LO 7.3 I don't have this "fixed
content" pre-checked and in LO 7.4 I did.

Why this behavior changes from LO 7.3 to LO 7.4 version? It's the same document
with two different behaviors.

When Justin L says "(Unfortunately, LO needs to be extended to support both
visual compatibility and F9 update-ability.)".

What "needs to be extended" is? Is some software to be installed?

Is there anything that I can do to maintain the behavior of the LO 7.3 version?
In other words, is there anything that I can do to this custom fields update
automatically?

I appologize my lack of knowledge on this subject.

Thank you all again,
Giovani Valle Dalbosco

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-08-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

Justin L  changed:

   What|Removed |Added

 CC||giovani.dalbo...@gmail.com

--- Comment #7 from Justin L  ---
*** Bug 156499 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-08-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

Justin L  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||7861

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-07-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

--- Comment #6 from Justin L  ---
I started putting some notes together about fields. I hope it helps. Feel free
to modify/update the wiki document.
https://wiki.documentfoundation.org/Documentation/Fields

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 98284] FILEOPEN: DOC: Fields do not auto-update on file open in MS Word, but they do in LO.

2023-05-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98284

Justin L  changed:

   What|Removed |Added

   Hardware|x86-64 (AMD64)  |All
Version|4.4.7.2 release |Inherited From OOo
Summary|FILEOPEN: doc import:   |FILEOPEN: DOC: Fields do
   |What's "MACRO CARRIER"? |not auto-update on file
   ||open in MS Word, but they
   ||do in LO.
 Blocks|104527  |113200
 OS|Windows (All)   |All
 CC||jl...@mail.com

--- Comment #5 from Justin L  ---
I know this problem very well, but I don't see an existing bug report about it.

MS Word does not automatically update fields to point to their variable values
on file open. Instead, it just displays the last-saved-text. It is only when
the user selects the field and presses F9 that the contents of the field change
to match the variable's value.

In this document, when the field is updated, it displays MACRO CARRIER - which
is the File - Properties - Title of the document.

LO automatically displays the variable in the field, and updates as soon as the
variable changes (which seems very sensible...).

So for compatibility, LO needs to add a flag to variables to soft-lock the
imported contents until they get an user-initiated refresh.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104527
[Bug 104527] [META] DOC (binary) format bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=113200
[Bug 113200] [META] DOC (binary) field bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.