Hi Tim.

Could we please have a thread for tracking known bugs/ issues.


- Steve

Nexy someone will suggest a Wiki, or using buzilla. These newbies . . . .

Yeah I know it's hopeless, but I just want to chime in:

Public accessible bugtracking (at least for registerred users) -> desperately needed!

Paul,
No harm meant.

Its just that Jol and I have asked for this for years. Year after year, the same little bugs and UI quirks come up, and few ever get addressed. I am sure that a decent tracking system would help, but the powers that be don't appear to want that sort of thing.

Personally after many years of bug reporting, beta testing and UI suggestions I have become incredibly cynical and have given up hope that things will improve substantially any time in the foreseeable future. Thats why I have given up testing betas. Too much work, for not enough return.

That said, I am looking forward to the release of ASICS 19, multithreading, and better blending.

To my point ... and now that I'm angry about losing my message, I make no excuses for being blunt !

I appreciate all the work that's gone on .. and Tim has been amazing with his fireman's hose

Tim is indeed brilliant

As alluded to though, there is something WRONG !

(If we take a quick look around the living room, we may just find a large grey thing with wrinkles)

I'm glad we have all this fresh blood on the forum since VC came about - it's certainly been a breath of fresh air .. and it's allowed a few of us (now somewhat cynical) old timers to step back a bit

I think in particular, it's helping to address another long term problem we've had .. CONSISTENCY

More importantly perhaps, I theorise that this program covers way TOO MUCH GROUND to be improved and maintained by such a SMALL team.

As far as I'm aware, there is still NOBODY within the organisation that uses VC/SHARK as their design tool - I think this is a problem

There are FUNDAMENTALS which were wrong in 2000 and they're still wrong today. Both Perspective and Feature Tree for example DON'T WORK on various levels

In NZ, I stopped endorsing it's use for this reason

Key to all this of course ... there has never been any method for effectively dealing with QA in this organisation.

YOU are the QA dept.

I've never felt this was right, but accepted it as the price I've had to pay to get a half decent CAD app on my Mac

I have petitioned the powers that be at Punch!, but never had a satisfactory response. I suggest you do the same if you have concerns

Till this is addressed, it will remain for me the best CAD program that was NEVER finished

end rant

no need to log out .. I'm sure that will be done automatically ; )

I vote for bug tracking, the benefits are obvious. It doesn't have to be public, could easily be for registered users only.

I strongly disagree that features are more important than stability and consistency. Time, however, and the market will tell.



Here here.