https://bugs.freedesktop.org/show_bug.cgi?id=47680
Michael Meeks michael.me...@novell.com changed:
What|Removed |Added
Status Whiteboard||EasyHack,DifficultyBeginner
||,SkillCpp,TopicUI
Summary|EDITING: Password bypassed |EasyHack: Password bypassed
|when recording changes |when recording changes
--- Comment #1 from Michael Meeks michael.me...@novell.com 2012-03-26
04:02:56 PDT ---
Gosh, a feature I never used yet :-) The semantics are to allow another
commenter to add/change stuff, but not to be able to remove existing red-lining
? if so I see what's up :-)
I imagine this is down to the new: FN_REDLINE_ACCEPT_DIRECT etc. items that
were added to make this more ergonomic not having the right sensitivity.
I guess that this code:
sw/source/ui/uiview/viewstat.cxx (GetState)
case FN_REDLINE_ACCEPT_DIRECT:
case FN_REDLINE_REJECT_DIRECT:
{
SwContentAtPos aCntntAtPos( SwContentAtPos::SW_REDLINE );
Point aCrsrPos = pWrtShell-GetCrsrDocPos( sal_True );
if( !pWrtShell-GetContentAtPos( aCrsrPos, aCntntAtPos ) )
rSet.DisableItem( nWhich );
}
Is simply not powerful enough to notice and adapt to this change-track
password-protection, and that some code from the existing changes accept/reject
logic needs inserting into there.
Turn into an easy-hack.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
