Author Topic: Altium 14: Browse Violations working?  (Read 3262 times)

0 Members and 1 Guest are viewing this topic.

Offline toohecTopic starter

  • Contributor
  • Posts: 36
  • Country: us
Altium 14: Browse Violations working?
« on: January 28, 2014, 01:52:22 am »
Our company just upgraded to Altium 14 (14.1.5), and the 'Browse Violations' command in the PCB layout does not appear to function at all anymore in this release.  Typically on previous releases I'd hover over the object(s) containing violations, and press Shift+V and a dialog box would pop-up displaying the objects and the rules that are in violation between those objects.  The 'Tools' menu still shows the 'Browse Violations' command and its associated Shift+V shortcut, but neither one appears to do anything anymore.  I still have the "PCB Rules and Violations" tab which will display all the violations, but it's not nearly as nice to use since it lists all the violations on the board, and not just the ones pertaining to the objects that my mouse pointer is hovering over.  Ugh!

Is this a bug in the current release?  Anyone else have any luck using this command in Altium 14?

EDIT: Not as big of a problem as I originally thought.  See next post for update.
« Last Edit: January 28, 2014, 02:36:45 am by toohec »
 

Offline toohecTopic starter

  • Contributor
  • Posts: 36
  • Country: us
Re: Altium 14: Browse Violations working?
« Reply #1 on: January 28, 2014, 02:35:44 am »
Ok... It appears that the problem is limited to polygon violations.   The Browse Violations function works as intended for any non-polygon objects.  In my case above where I discovered the problem, I had a single polygon to polygon clearance violation, and could not get the browse violation option to work at all.  After I purposely added other violations to test the browse violation functionality,  I discovered that it works normally for all other object types.  I don't recall having this problem on the previous Altium releases, but maybe I'm wrong.  At least the bug (if it's new to A14) isn't as bad as I thought, and it's usually not too critical for polygon related violations anyway.

 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf