help - skill code for goto xy coordinate

Hi,

>> Thanks Riad for another code. but yours does not have the "X" mark ruler

If you were really listening to what other people said, then you would have realised that my routine has the ‘X’ as well.

As per Andrew’s recommendation, I have added into the code the following:

leSetRefPoint(windowId~>cellView point)

But since we all have different tastes, I did not want to force the environment to display the reference point.

Instead, you end user can go to the VLE->Options->Layout Editor->Display Ref Point

Well, If you have carefully read through the code, you would have realized I have put the following in comment:

    ;unless(leEditorOptionsForm->options->displayRefPoint->value
    ;  leEditorOptionsForm->options->displayRefPoint->value=t
    ;)
So to answer your question: the X is created, it’s down to you to display it !

Marking with rules is just fiddling around, I don’t like fiddling.

>> and it's too zoomed in.

Again, it would have been better if you read my comments.

My routine has got a dynamic zooming scale. Say you are working on a block level design whose size is 100u*100u. Say a zoom by 100 would be alright for you. But if you move to a chip level layout then a zoom by 100 might be not enough. My routine does all dynamically to fall into a window which is less than 1um square. I have setup this given the technology node I’m working with. This might be too much for some people and may be not enough for others. That’s why I have said in my commented code how to make flexible. Basically by adding a multiplier. You can make it >1 or <1, depends on you wanting more zoom out/in. Again, please read the comments.

>> and could there  be a seperate input box for x and y coordinates?

I do not like the separated coordinates, simply because you loose productivity. Again, when you get an error from Assura/Calibre (I think I have written this for Calibre corrdinates) saying something occurred at that point, then it easier for people just make a cp/paste as Derek advised.

At the end, I do concur with Andrew’s and Derek’s; you better take this as an idea to start with rather than a tailored suit ready to wear!

Scripting is all about practice and you need to put your hands on mate!

 
Cheers,

Riad.

Hi,

>> Thanks Riad for another code. but yours does not have the "X" mark ruler

If you were really listening to what other people said, then you would have realised that my routine has the ‘X’ as well.

As per Andrew’s recommendation, I have added into the code the following:

leSetRefPoint(windowId~>cellView point)

But since we all have different tastes, I did not want to force the environment to display the reference point.

Instead, you end user can go to the VLE->Options->Layout Editor->Display Ref Point

Well, If you have carefully read through the code, you would have realized I have put the following in comment:

    ;unless(leEditorOptionsForm->options->displayRefPoint->value
    ;  leEditorOptionsForm->options->displayRefPoint->value=t
    ;)
So to answer your question: the X is created, it’s down to you to display it !

Marking with rules is just fiddling around, I don’t like fiddling.

>> and it's too zoomed in.

Again, it would have been better if you read my comments.

My routine has got a dynamic zooming scale. Say you are working on a block level design whose size is 100u*100u. Say a zoom by 100 would be alright for you. But if you move to a chip level layout then a zoom by 100 might be not enough. My routine does all dynamically to fall into a window which is less than 1um square. I have setup this given the technology node I’m working with. This might be too much for some people and may be not enough for others. That’s why I have said in my commented code how to make flexible. Basically by adding a multiplier. You can make it >1 or <1, depends on you wanting more zoom out/in. Again, please read the comments.

>> and could there  be a seperate input box for x and y coordinates?

I do not like the separated coordinates, simply because you loose productivity. Again, when you get an error from Assura/Calibre (I think I have written this for Calibre corrdinates) saying something occurred at that point, then it easier for people just make a cp/paste as Derek advised.

At the end, I do concur with Andrew’s and Derek’s; you better take this as an idea to start with rather than a tailored suit ready to wear!

Scripting is all about practice and you need to put your hands on mate!

 
Cheers,

Riad.