Virtuoso graphical window - get absolute scale

Hi,

I think you need hiGetViewBBox()

hiGetViewBBox( 
  [ w_window ] 
)     => l_bBox

So you don't get a 'scale' just the viewing area as a bounding box.

Best regards,

Lawrence.

Lawrence,

You beat me to it. I was just looking at some very old code to copy the zoom level of one window to another:

/* abCopyWinView.il

Author     A.D.Beckett
Group      Structured Custom, Cadence Design Systems Ltd
Machine    SUN
Date       Apr 25, 1994 
Modified   
By         

Copies a window view from one window to another,
not necessarily of the same cellView

***************************************************

SCCS Info: @(#) abCopyWinView.il 11/20/08.15:26:12 1.1

*/

(procedure (abCopyWinViewCB win done points)
  (let (bbox)
       (setq win (hiGetCurrentWindow))
       (when (and done (windowp win) (windowp abCopyWinViewFrom))
             (setq bbox (hiGetViewBBox abCopyWinViewFrom))
             (hiZoomIn win bbox))))

/***************************************************************
*                                                              *
*             (abCopyWinView @optional (win nil))              *
*                                                              *
*     Procedure to copy a view from one window to another      *
*                                                              *
***************************************************************/

(procedure (abCopyWinView @optional (win nil))
  (unless win (setq win (hiGetCurrentWindow)))
  (setq abCopyWinViewFrom win)
  (hiSetCurrentWindow win)
  (when (windowp win)
        (enterMultiRep ?prompts '("Point to the source window" "Point to the destination window")
                       ?points '((0 0))
                       ?doneProc "abCopyWinViewCB"
                       ?dontDraw t
                       ))
  t)

The absolute scale could be computed (if you were really keen on doing so) by figuring out the ratio between the cellView bBox and the hiGetViewBBox (I'm assuming it will be the greater or smaller of the width or height ratios, but that's a guess and I've not done the experiments). I'm not sure how useful that would be.

Andrew

If you want them at the same absolute scale, and centred in the same spot, then I think you'd just use hiGetViewBBox and hiZoomIn - that would effectively do the same thing - they'd both be showing the same zoom area, which I think is in effect the same as what you're asking...

Andrew

Not sure if that works when the windows are different sizes.  hiZoomIn uses relative scale - hopefully once the windows are initially set to the same absolute scale, then you can do the same relative zooms from then on.

caver456 said:

hiZoomIn uses relative scale

No, it doesn't. It zooms to an absolute bounding box. hiZoomRelativeScale zooms using a relative scale, and that's not what I'm using here.

I originally wrote this code 27 years ago to allow me to have two windows open (such as an extracted view and a layout view, or two layout views on the same design) and replicate the zoom region in one window from another (even if the windows are different sizes).

There's not really a concept in the window itself of keeping track of an "absolute scale".The absolute scale is just a means of determining how much of the overall bounding box of the cellView should be displayed in the window.

Andrew.

Ah - sorry bout that, I was thinking of hiZoomInAtMouse / hiZoomOutAtMouse / hiZoomWindowAtMouse etc that use relative scales.  Anyway I will give this code a shot verbatim - I didn't grasp initially that it should be a full solution.  Thanks

We can achieve the similar functionality with the help of hiRegZoomPanProc(). I use this to sync two windows simultaneously.

-Ramakrishnan

I had high hopes for hiRegZoomPanProc but I kept encountering errors like this, which remained even after I unregistered the proc:

; `>a^\(window(2) list(list(-194.00000 -754.96400) list(3243.78600 2389.96400)))
; ^
; SYNTAX ERROR found at line 1 column 2 of file *string*
; *Error* lineread/read: syntax error encountered in input

This is on IC6.1.7-64b.500.18.  All in all it seemed a bit less spooky / a bit more controllable to just intercept the pan/zoom operations.

But, I would be very curious to see your implementation.  Thanks

Hi Andrew, I did try your code - I think was jut not clear about my use of the term "scale".  What I'd like to do is match the pixels-per-micron from one window to another, so that e.g. a 3-microon-wide-resistor in one large window, zoomed such that it is an inch wide on the screen, would also take one inch on the screen when viewed in a much smaller window.  If the two windows are identically sized, then your code accomplishes this pixels-per-micron matching.  I guess my use of the term 'absolute scale' was incorrect.

I'm not sure that's really doable. You'd need to know the number of pixels on the canvas itself together with the hiGetViewBBox - and then use that to compute the equivalent zoom area in the other window using the canvas size of that window. You can find the screen coordinates (in pixels) of the entire window, but that includes the toolbars, assistants and so on, but not sure there's a way of finding the canvas area in pixels.

Andrew.

I'll probably just go with the entire window size, figuring/hoping that it's "close enough", and see how that goes.  Regardless, thanks for your quick help.

I'm not sure of your requirement. But registering and unregistering the zoom pan proc are not problematic and I was able to sync two windows. The implementation was quite simple; Get the window coordinates that come from the callback and apply to the target window.

With ICADV20 version, I see only zoom events are getting triggered by hiRegZoomPanProc(). In previous versions, any layer visibility change was triggering the callback. I have not checked through the documentation for this behaviour

-Ramakrishnan

I'm not sure of your requirement. But registering and unregistering the zoom pan proc are not problematic and I was able to sync two windows. The implementation was quite simple; Get the window coordinates that come from the callback and apply to the target window.

With ICADV20 version, I see only zoom events are getting triggered by hiRegZoomPanProc(). In previous versions, any layer visibility change was triggering the callback. I have not checked through the documentation for this behaviour

-Ramakrishnan