On 10/13/2014 07:53 AM, Werner Schweer wrote: > Only elements which are visible are supposed to have a meaningful > bounding box. > Bbox is mainly used to calculate which elemens we need to redraw on an > exposure > event.
OK, thanks, that makes sense. I guess it's also used to figure out which element we are clicking, but again, there is no need for this to make sense on elements that are not meant to be visible. > Segment has a maintained x-position but no width if i remember right. > Chord bbox is set and is the outline of all siblings. I am not sure its > still used anywhere. I'm not sure either. But it's not always correct currently. At least, I have found a few cases where it is wrong. So far, though, I haven't seen any bad effects, which makes me suspect we don't really use it. I'm not sure I want to try to "fix" these cases if there are no actual problems currently - I'd be afraid of breaking something that used to work. > If the segment bbox is of interest it would be better to recalculate the > values from > context (next segment, staff position etc.). I had been trying to use it position the end of an ottava, and it worked well except in the cases where the segment bbox was not set well. But I now think using the segment bbox is the the wrong approach anyhow. It causes the length of an ottava line to be possibly affected by elements on other staves, which is not really appropriate. So I am now instead looping through the voices on the current staff and taking the rightmost edge of any chord I find, which is more directly what I want to achieve anyhow. Segment bbox width just happened to produce a similar result "most" of the time. Calculating width by looking at the position of the next segment is too big - it would include the space up to the next chord, which is specifically what we are trying to avoid for ottavas. Marc ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
