Actions
Forum Thread Details
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 85 subscribers
  • Views 410 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug Update

harvie256

In September I asked for feedback at pcbsoftware@element14.com on two bugs I reported:

https://www.element14.com/community/thread/56534/l/bug-report-pcblib-inspector-unable-to-change-multi-layer-pads-to-single-layer

https://www.element14.com/community/thread/56533/l/bug-report-non-simple-pads-not-saving-correctly

 

The response I got was:

"I will of course ask the questions for you and relay the information as soon as I get it."

 

Is there any update on these bugs and if fixes have made it into the V1.3 that's keeps being advertised.

 

Regards

  • 0

    Hi,

     

    I have resubmitted these to the developers and will let you know the status as soon as they respond.

     

    Tony

  • 0

    Hi,

     

    I am sorry that you did not get responses to these bugs previously.  However, here are the responses I received from the developers:

     

    Multilayer: Thank you for reporting this bug. The software should set the hole size to zero instead of forcing back to Multilayer, however it currently is designed only to react to the non-zero hole size and set the pad to multilayer. This behavior also exists in Altium Designer and any changes need to be addressed in both places so would need some priority to be addressed.  The best way to use the PCB Inspector for this operation is to first set the hole size to 0 and then change the layer from Multilayer to another layer.

     

    Non-Simple Pads: Thank you for reporting this issue. This is logged as a bug for consideration in CircuitStudio 2.0 but unfortunately won't make it into version 1.3.

     

    Let us know if we can be of further assistance.

     

    Tony

     

     

  • 0 in reply to e14softwareteam

    Thanks for the reply.

     

    That's a completely usable work around for changing the pad to single layer.  Sounds like a fix isn't going to make it into CS or AD in the near future, so perhaps documenting this behaviour and the work around in the product manual would be an appropriate short term solution.

     

    This is the first I've heard of CS 2.0.  Do you have a road map of expected release dates (roughly of course)?

     

    Thanks for your help.

  • 0 in reply to harvie256

    harvie256,

     

    The roadmap is ever evolving (and always subject to change!) but v2.0 is targeted for around 2Q17 with a tentative point release, beyond v1.3, scheduled sometime between now and then.

     

    Pete