Is this all that was pushed out in this update?
If it took 6 months to get just that fixed, then something must have gone horribly wrong...
AZERTY support is in, the pop-up bottom row icons aren't cut off, there is undoubtedly more, but it would have been nice if they mentioned what they've been working on and what's supposed to be fixed in this update.
Now we'd have to try everything all over again.
Parametric cells are still placed on the active level, labels without leader still broken, wrong terminators on DWG dimensions still there.
Better not get our hopes up too high.
Trimble? Merge with sketchup?? Noooooooo.... What we need is:
Fixes and updates for old stuff;
Proper merge with vue: CE u2 and beyond;
Update for luxology engine 10 (by the time we get that probably it's already out 11 or so...);
Refinement for UI;
To reiterate what Dan Eng has said above...we have recently reinstated the SR notification system, and he is looking into this and will post an update about it.
We are certainly appreciative of the software choices you make and the effort you all take to report your issues and as demonstrated by the list posted here are happy to post the issues fixed in each build. This should save you the time it takes to re-verify your defects at each release; especially important since releases will now come far more frequently.
Also, regarding Ian's effort to collect issues together in a list here. It may be useful for you discuss and decide on the highest priority things if it reveals which issues help the largest number of you. We will carefully review it and use it to guide our work in the coming updates. However, as Andrew states, if you are indeed production-down or need specific fixes urgently, please raise a Service Request so that we can be sure to properly trace the issue.
Makai Smith said:This should save you the time it takes to re-verify your defects at each release; especially important since releases will now come far more frequently
Sorry but it really doesn't. On the user side there is no cross reference between and SR and a Defect number. There is no way to run a defect number against my SR's
The SR Database does have a field the shows status but they don't seem to get updated went the issue gets fixed.
The SR filing is unnecessarily complex.
With connect I can open right to my SR's but....
I have select my product for a Picklist of over 100. Who in their right mind creates a pick list with over 100 entries?
I have to give it a version number. & language... remember I'm launching for the product itself.
Why can't any of this be auto populated? At least remember the last settings.
Fortunately there are some extremely helpful BSI personal here in the form who will take defects logged here and file the SR for us. This saves me a lot of time having to file everything twice and eliminates BSI having two different people chasing down the same problem.
Why aren't there more Bentley Support/Developers active in here.!!!!!
Case in point how this wonderful system works...NOT!
Defect 323991 which is reported as fixed.
This was a result of SR 7000416380 which is still showing me its an Open Defect.
And the only way for me to find the link between the two was to read thru all Descriptions and look for similarities.