Freezing improves performance. That’s the difference.
A tyro to AutoCAD will immediately notice that he or she has two options available to him – both of which ostensibly render similar results: freezing a layer and turning it off. But what is the real difference?
When you turn a layer off, it is still loaded into memory. AutoCAD is keeping track of it.
When you freeze a layer, then AutoCAD basically ignores that layer and everything on it. You should notice a slight increase in speed and performance when you freeze layers – especially if they contain hundreds of thousands of elements. That will give you a significant performance boost cf: if you simply turned that layer off.
That’s the difference and I hope you learned something.
How are you going to identify one duplicate in a sea where everything looks the same?
Duplicates are a problem – an expensive problem, especially if you are dealing with hundreds and perhaps even over a thousand panels. Somebody cocks up – usually on the client side – but how are you meant to identify it?
You could manually do it, but then that will more than likely take a long time. Or you could just employ Tek1 to do that sort of thing for you. Here is a video demonstration:
It can work for all clients with only very minor modifications. Very well abstracted out in the code.
It is super fast. Comparing the thousands of elements in each drawing takes a bit of computing power – but with smart algorithms, you can cut down the time.
It can work in the marking plan and elevation or layout. The same code, the same command, but x3 the power.
Demonstrates how to save a view in AutoCAD – please watch this gif carefully. It’s pretty self explanatory.
It can get pretty annoying zooming and moving back and forth between a panel and another panel. You can eliminate a lot of the panning involved by saving a “View”.
Open the View Manager (e.g. type in “View” in the command line and press ENTER, or you can see another way of doing this in the gif image above.)
Create a new View.
Refer to it when required.
AutoCAD will now automatically take you to what you want to se.
Showing how to open limited geometries using partial open.
Suppose your .dwg file has hundreds of thousands of entities all over the place – but you don’t want to see all of them at once – or load all of their geometries. This is especially the case when dealing with Bubble Deck layouts. You can only open the things that you need via a partial open. You can now choose and view only the stuff that you want to see. It’s quicker than otherwise.
Showing a sample elevation panel with deliberately misplaced panel elements.
This is big. Huuuuge! I’ve talked before about our ability to easily cross check between the Layout and Shop drawings. Now you can cross check from the other direction – when you are in the shop drawing, you can now check the corresponding panel which exists in the layout.
You can clearly see any differences.
So now if someone moves a ferrule or a cast in plate etc. you will be able to easily see those changes.
It could save you from some expensive errors.
Here is the demo. I hope you enjoy it!
It can work for all clients with only very minor modifications. Very well abstracted out in the code.
It is super fast. Comparing the thousands of elements in each drawing takes a bit of computing power – but with smart algorithms, you can cut down the time.
It works for all sorts of edge cases – what if the panel was made up of arcs, polylines and straight lines – this plugin can handle all sorts of things. It can also handle voids.
We have 2 positions available now at our Koyambedu Office as of 30/03/2019.
You will be required to attend an online test from home. If you pass the test from home, then we will call you for a test in our office in Koyammedu Chennai for further test and interview.
Please brush up your basic engineering mathematics, logarithms. Please be prepared with Paper, pen, good internet connection and a calculator.
Test are timed and will close within 1 hour.
Please fill in this form and we will send you a URL, username, and password to take the online test when positions become available.
If there’s a very high learning curve involved in using your software – chances are that a lot of people simply will not use it.
This post details an important issue in programming (and in the development of solutions which solve certain problems): the problem of human nature. It outlines my experience and the lessons which I have learned. I will share them for the benefit of
our readers.
What happened? What was the problem?
I had originally created all the data a client needed and more – streamlined and efficiently placed in pivot tables – in neat rows and columns that allow you to configure and query the data to find out anything and everything you need to know. To me it was a no brainer – surely they’d opt for this solution over the earlier inefficient solution. This data basically was a list of items that needed to be ordered, their quantities, and lengths, listed by the panel number which they were to be cast in. It’s like giving you the power of the sun, but in the palm of your hand. It’s amazing!
I presented this solution to the client, hoping that they would appreciate it and understand its value, its beauty and simplicity. It sure beat the old fashioned way by which items were ordered: hand counted and then manually compiled into a table in AutoCAD – of all places – yes you read correctly, in AutoCAD, not Excel or some RDMS. From AutoCAD, revisions are nearly impossible to track, especially when you have thousands and thousands of items to be ordered. And from there, from the AutoCAD drawing, that data is then again **manually** recompiled into another Excel spreadsheet that sits at the client office. There is so much duplication, needless inefficiencies, and the potential to make costly mistakes. It’s crazy!
What if there were revisions to say, 100 panels? Wouldn’t it be handy to know that you don’t need to order an extra 30 or so cast in plates (given they were previously ordered) – and cast in plates ain’t cheap? It’s a walk in the park for a pivot table. But there just one problem: that was not what the client wanted.
What was the lesson to be learned?
Nope: the client wants their data presented in a certain way, in a certain style. Pivot tables are a whole new kettle of fish. The client does not want Excel. The client wants AutoCAD. And moreover, that data must be presented in a certain style: red text, white lines, and the curious anomaly of those sheets having the same data unnecessarily repeated numerous times throughout the same page. Now that’s fine by me. But it raises a very important lesson which is worth sharing:
Don’t depart too far from what your users are used to. If you do, they simply won’t use it or appreciate your solution. In this case, the pivot tables were too big a leap. It is not easy and it’s complicated. It’s like presenting to users Git, and telling them that it will solve all their version control problems – when those users are used to simply “Saving As” – as their version control system. It’s too big a leap and too far a learning curve.
Give them what they want: Your customer wants red text. Give that to him. Your customer wants white lines: give that to her. Sure, you have an obligations to suggest other alternatives which may be of benefit to them – but at the end of the day, it’s their call. Don’t argue with them about what is best for them: shut up and simply give ‘em what they want! This is the most important lesson that I learned.
