Pillowcase Posted December 8, 2007 Report Posted December 8, 2007 This has been a problem for quite a few versions now: if the Pieces/Blocks column is shown with the Priority or Mode columns it sort of gobbles them up and treats them as part of itself. In other words it expands the graphic until both (or all three) appear to be one big Pieces/Blocks column.
jewelisheaven Posted December 8, 2007 Report Posted December 8, 2007 ... screenshot? I have all columns enabled in all panes and do not see this.Also on what build and OS version are you experiencing this on.
Pillowcase Posted December 8, 2007 Author Report Posted December 8, 2007 If you turn them all on it won't show up. It only happens when those are the only columns turned on. The version I'm using is 1.7.5
jewelisheaven Posted December 8, 2007 Report Posted December 8, 2007 OK I can confirm that indeed happensI must state it's a conditional though. The default? or just the way my setup is, under Pieces the barchart is already to the left of the other columns, so they appear fine on the right. It is indeed only when the Blocks column is posterior to Priority and Mode that it appears to start at 0,0 and go until the end of its column.
Pillowcase Posted December 8, 2007 Author Report Posted December 8, 2007 No, actually it just appears to be that way. When those 2 columns are on the right they are actually covering part of the bar. For proof of this turn those columns off and on while they are on the right side and the bar should shrink and expand. Also, if you were actually downloading (in other words if the bar graphic was being modified) you would see the bar intermittently flash out from underneath. I presume from your screen shot that you are using a completed download to test this. That's probably why you can't see the bar changing shape. I suggest you try it with an unfinished one, or even better one that's in the process of downloading.
jewelisheaven Posted December 8, 2007 Report Posted December 8, 2007 In either case we can't do anything about it. Hopefully someone comes along to see it for the next update
Pillowcase Posted January 10, 2008 Author Report Posted January 10, 2008 It is? I'm using 1.8 (7676) now and the problem still occurs.
jewelisheaven Posted January 10, 2008 Report Posted January 10, 2008 That was posted in the 1.8 thread, and there hasn't been a new build yet, so I'm not surprised
Firon Posted January 10, 2008 Report Posted January 10, 2008 Fixed doesn't mean fixed in the currently released build.
Ryan Norton Posted January 11, 2008 Report Posted January 11, 2008 It'll say in the changelog for the alpha or whatever the released version is.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.