Tweet
V3.7 mr3 complaints FIX THIS STUFF
Well, I started programming today in V3.7 MR3 (previous V3.5, no mr) and here is a list so far....
1) When doing CTRL-E to execute a single point you now have to have the curson ON the feature itself, placing it at the end of it's dimension that is immeadiately following no longer works, so when you 'forget' you moved the cursor, the next feature gets put between the previous feature and it's dimension and if you have auto dimension turned on, the dimension ends up between them as well.
2) When doing SHOW PATH LINES, it does move all the points back to the nominal location (actually, the target location) but it will NOT show the dimensions at nominal location. V3.5 would put the dimensions back to nominals after you saved, closed, and re-opened the program, V3.7 MR3 will not do it until you re-type in some of the feature ID's for the dimensions.
3) The spacing between the columns in the report (I've mentioned this before) is set way too dang high! Are they using those big, wide printers at B&S/Wilcox for the development of this software instead of a deskjet like all of us have? Using metric, and 3 decimal places (pretty much standard, eh?) and using +/-1.5mm tolerance, there are 3 empty spaces in front of the tolerance that are part of the tolerance 'column'. You can put in a tolerance of 99,999.000 and that will just fill in the amount of default space they have for the tolerance. Now come on! Who gets that kind of tolerance? And, if you increase the tolerance to 100,000.000, it makes the columns wider. If the width of the column is going to adjust itself, it should default to a width for a tolerance of -1.500 (2 places before the decimal, 3 after) then get wider if needed. I have never seen anything with more than 5mm of tolerance, let alone 99.000 mm of tolerance (which is what the defaul width should be, as far as I am concerned). There are, by design, 2 blank spaces between the columns, not including the width of the columns in which the numbers show up.
That's all I've found for now, but then, I have only been programming in this version for 3 hours, so I am sure there will be more additions later.
1) When doing CTRL-E to execute a single point you now have to have the curson ON the feature itself, placing it at the end of it's dimension that is immeadiately following no longer works, so when you 'forget' you moved the cursor, the next feature gets put between the previous feature and it's dimension and if you have auto dimension turned on, the dimension ends up between them as well.
2) When doing SHOW PATH LINES, it does move all the points back to the nominal location (actually, the target location) but it will NOT show the dimensions at nominal location. V3.5 would put the dimensions back to nominals after you saved, closed, and re-opened the program, V3.7 MR3 will not do it until you re-type in some of the feature ID's for the dimensions.
3) The spacing between the columns in the report (I've mentioned this before) is set way too dang high! Are they using those big, wide printers at B&S/Wilcox for the development of this software instead of a deskjet like all of us have? Using metric, and 3 decimal places (pretty much standard, eh?) and using +/-1.5mm tolerance, there are 3 empty spaces in front of the tolerance that are part of the tolerance 'column'. You can put in a tolerance of 99,999.000 and that will just fill in the amount of default space they have for the tolerance. Now come on! Who gets that kind of tolerance? And, if you increase the tolerance to 100,000.000, it makes the columns wider. If the width of the column is going to adjust itself, it should default to a width for a tolerance of -1.500 (2 places before the decimal, 3 after) then get wider if needed. I have never seen anything with more than 5mm of tolerance, let alone 99.000 mm of tolerance (which is what the defaul width should be, as far as I am concerned). There are, by design, 2 blank spaces between the columns, not including the width of the columns in which the numbers show up.
That's all I've found for now, but then, I have only been programming in this version for 3 hours, so I am sure there will be more additions later.
Don't be so optimistic
Comment