I have numerous AttrDXL displayed in columns, summarizing this or linked objects, and folks are getting frustrated trying to edit these columns. I wonder how best to indicate that these columns (layout and attrDXL) are not editable.
llandale - Wed Jun 02 14:17:21 EDT 2010 |
Re: Indicate no-edit columns I've never used triggers, but is it possible to set a trigger that runs each time a view is opened ? If yes, why not set the background color of these columns (columns such as col.dxl is not empty) to a specific color that would mean "read only" ? Alain |
Re: Indicate no-edit columns This should work with attributes and DXL layout - I see no other way of coloring attribute DXL. Just a thought, Regards, Mathias Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS |
Re: Indicate no-edit columns Mathias Mamsch - Thu Jun 03 03:33:26 EDT 2010 Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
If you do a Word export to DOORS from a Word document which has Word higlights (colored background for text) the higlight will be left in DOORS. I copied the highlight RTF codes and applied it to a DXL attribute - it seems that a DXL attribute can at least display a colored backround for the text.
// integer/string/text number of modifications
/*
Attribute DXL type : INTEGER, STRING or TEXT (autosensing)
*/
string GrayBackStart = "
{\\rtf1\\ansi\\ansicpg1252\\deff0\\deflang1033{\\fonttbl{\\fo\\fnil\\fcharset0 Tahoma;}}
{\\colortbl;\\red128\\green128\\blue128;}
\\viewkind4\\uc1\\pard\\highlight1\\lang1035\\f0\\fs20 "
string GrayBackEnd = "\\highlight0\\lang1033\\par}"
int getMods(Object o) {
History h
int count = 0
for h in o do {
count++
}
return count
}
int val = getMods obj
Module m
AttrDef ad
AttrType at
m = module obj
ad = find(m,attrDXLName)
at = ad.type
if (at.type == attrInteger)
obj.attrDXLName = val
if ((at.type == attrString) || (at.type == attrText))
obj.attrDXLName = richText(GrayBackStart "Modifications: " val GrayBackEnd) ""
|
Re: Indicate no-edit columns SystemAdmin - Thu Jun 03 07:01:33 EDT 2010
If you do a Word export to DOORS from a Word document which has Word higlights (colored background for text) the higlight will be left in DOORS. I copied the highlight RTF codes and applied it to a DXL attribute - it seems that a DXL attribute can at least display a colored backround for the text.
// integer/string/text number of modifications
/*
Attribute DXL type : INTEGER, STRING or TEXT (autosensing)
*/
string GrayBackStart = "
{\\rtf1\\ansi\\ansicpg1252\\deff0\\deflang1033{\\fonttbl{\\fo\\fnil\\fcharset0 Tahoma;}}
{\\colortbl;\\red128\\green128\\blue128;}
\\viewkind4\\uc1\\pard\\highlight1\\lang1035\\f0\\fs20 "
string GrayBackEnd = "\\highlight0\\lang1033\\par}"
int getMods(Object o) {
History h
int count = 0
for h in o do {
count++
}
return count
}
int val = getMods obj
Module m
AttrDef ad
AttrType at
m = module obj
ad = find(m,attrDXLName)
at = ad.type
if (at.type == attrInteger)
obj.attrDXLName = val
if ((at.type == attrString) || (at.type == attrText))
obj.attrDXLName = richText(GrayBackStart "Modifications: " val GrayBackEnd) ""
Clever solution.
string GrayBackStart = "{\\rtf1{\\colortbl;\\red128\\green128\\blue128;}\\highlight1 "
string GrayBackEnd = "}"
|
Re: Indicate no-edit columns Mathias Mamsch - Thu Jun 03 03:33:26 EDT 2010 Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS Thanks, this will do well enough, until some clown defines a Color Scheme featuring the exact color Gray I'll use. Thanks
Doh! Forgot to 'refresh DXL attributes' after making changes. |