Page 1 of 1

Bugs in new Beta v.2

Posted: Tue May 17, 2011 4:25 am
by blacklite
Hi Claude,

Just noticed a few bugs in the new Beta of LXBeams.

Firstly, if set to meters in the preferences the inspector still works in feet for input ie. if 3 is entered it get's changed to 0.91m. If a number is entered followed by "m" then it works in meters. This is different to how it used to work, and is quite frustrating as I keep forgetting to put the "m" in.

Second one is that unless I gave the numbering field of a position a category in the new Data Fields window it is impossible to use auto unit numbering or even access the drop down numbering selection tool in the inspectors position tab.

Am liking the 3D offset a lot though!

Cheers

Ben

Posted: Tue May 17, 2011 5:33 pm
by admin
The regression where the default numbering/spacing/layout options for positions was corrected in the previous latest build (5315). Position spacing now appears in the Inspector's info tab. Layout and numbering do not by default. However, the popups in the Inspector's Position tab can control those settings.

The ability to enter measurements in either English or Metric and have them convert is a new addition. In the latest build 1.9.4 (5317), the default is now to use meters or feet depending on the plot's ruler setting when no explicit units are specified.

If the plot is set to scale meters:
1' or 1'-0" is read as 0.91m
1 is read as 1m
1m is read as 1m

If the plot is set to scale feet:
1' or 1'-0" is read as 1'-0"
1 is read as 1'-0"
1m is read as 3'-3.5"

Posted: Tue May 24, 2011 12:04 am
by lanternz
Pro 1.9.4 build 5317. I am getting some unexplained crashes. It has happened while viewing beams and then clearing them. I have tried repeating all my recent actions but I can't reproduce it deliberately yet. Anyone else getting this with build 5317?

Posted: Tue May 31, 2011 5:18 am
by lanternz
Another instance of this continuing crash - change the instrument type and then zero the key block.

Posted: Tue May 31, 2011 9:41 pm
by admin
Please try this with the latest build 1.9.6 (5331) and see if it still occurs. 1.9.6 fixes a problem with the key block. 1.9.5 fixed some problems with beams and the model. There was a problem prior to 1.9.5 with attempting to draw a beam using a field angle when none was specified.