To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=44565
------- Additional comments from [EMAIL PROTECTED] Wed Mar 9 08:21:02 -0800 2005 ------- MAV->MSC: More specific criticism would be much more helpful. At the current state I still do not see why is the design so bad. MAV->FS: It is not just about the technical part. This is a logic of embedded object behaviour that in result affects user. An embedded object consists from replacement representation it provides to a container and own contents ( the replacement representation might be optional ). If somebody activates starwriter embedded object inplace, scrolls down and deactivates the object, the replacement image should reflect the changes, the embedded document should store those changes so that the next time user activates it the correct place of the document is shown. The same is true for outplace activation. For objects that support inplace activation it seems to be the only reasonable way. The only alternative in object behaviour that I see is acceptable only for outplace activation. In this case object document is always activated in specific hardcoded scrolling position and the replacement image is always generated only for this position. In this case the scrolling position is no more a part of the embedded document information, so the scrolling does not change the modified state of the object. Although technically it is no big problem to implement triggering of the second behaviour for embedded objects, from my point of view the second way brings no benefit, moreover, it contains only minuses: - It is not possible for user to let the object be activated at a specific position next time. For database it is even more valuable loss since by changing of the scrolling position in 'edit' mode user could specify the way the form is opened in 'open' mode, of course the scrolling in 'open' mode can not set the modified flag since the object is readonly. - ( questionable ) As I understand the left bottom window in the database component is designed to show form preview ( at least it was used for this reason sometimes ago ), means embedded object replacement image, if this feature is going to be activated then the previous entry becomes even more valuable. I just wanted to clarify my position since this change seems to be questionable for me even from user point of view. But as I have mentioned, if database requires the second way behaviour for forms, it should be no big problem from technical point of view. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
