SQL Server 报告服务条形图
我正在尝试创建水平条形图，使其看起来像药丸图。
我想要一个堆积条形图或 100% 堆积条形图，并将圆角末端放在该图表上。我只会使用图表中的 1 行。
我的一个想法是在图表的两端放置圆形图像来实现这一点，但我不确定这是否会带来单一药丸的光滑感觉。
有人有好的建议吗？
我并不局限于使用图表对象的想法。但我宁愿远离需要购买的第三方组件。
I am trying to create horizontal bar chart to look like a pill chart.
I would like to take a either a stacked bar chart or a 100% stacked bar chart and put rounded ends onto this chart. I would only be using 1 row within the chart.
One idea I had was just putting rounded images on either end of the chart to accomplish this but I'm not sure that this will give the smooth feel of a single pill.
Does anyone have a good suggestion?
I am not tied to the idea of using a chart object. But I would prefer to stay away from third party components that need to be purchased.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我必须同意吉姆康斯特布尔的观点，从某种意义上说
“数据诚实性”可能会受到严重损害，但是如果您愿意“偏离”代表弧线的数量，则可以向图表添加“假”点，以便图表3 段变为 5 段，1 段 5 变为 7 段。如果您向存储过程输出添加两列，一列用于左端，一列用于右端，则在报表设计器中设置背景图像的值。您还需要适应条形宽度始终超过 100% 的事实，因此如果您将每个端盖设为 5%，则必须将每个“真实”数据点的值设为 ( [期望值] * .9），以便这些“真实”数据点的总和为 90%，加上两个上限，每个上限为 5%。
不过，请注意：由于结果图表中固有的不准确之处，我能够说服提出此要求的客户，因此没有尝试执行我向您建议的操作，因此请继续小心。
它在理论上是有效的，但许多其他糟糕的想法也是如此
i'd have to agree with jimconstable on this, in the sense that
'data honesty' could be significantly compromised, but if you're willing to be "off" by the amount that represents the arc, you could add "false" points to the chart, so that a chart with 3 segments becomes one with 5, one with 5 becomes one with 7. If you add two columns to your stored procedure output, one for left end and one for right end, then set the value of the background image in the report designer. You'd also need to accomodate for the fact that the width of the bar would always exceed 100%, so if you made each of the end caps 5%, you would have to make the value each of the "real" data points ([desired value] * .9 ) so that the total of these 'real' data points would sum to 90%, plus two end caps at 5% each.
a word of caution though: i was able to talk the client who asked for this out of it by virtue of the inherent innacuracy in the resulting chart, and therefore haven't tried to do what i'm suggesting to you, so proceed with caution.
it works in theory, but so do lots of other bad ideas