How to use terminal Command in cadence CIW?

Probably ipcBeginProcess and then ipcReadProcess is what you need, but your question is far from clear.

Andrew

I was trying to get screen size in CIW to set by default window sizes using skill. But, in CIW I am not getting exact screen size I mean it is including control panel and all other to the screen size. is there any function it excludes control panel and give available screen size to use?

Well, hiGetMaxScreenCoords() will report the display size, but finding how much of the display is usable will almost certainly be dependent upon the window manager - I don't know of a way of getting that even from the command line (which works for all window managers)

xprop -root _NET_WORKAREA

Should work on the major window managers, the only one that I know, which does not support this, is olvwm but there the screen size is identical to the usable work area.
From the returned numbers, the first two are the x and y coordinates of the top left of the usable space, and the next two are width and height.

Regards,

Interestingly, hiGetMaxScreenCoords() returns a smaller height for me than the xprop output, which is smaller than the actual screen resolution (shown in xdpyinfo). Placing a window doesn't place it exactly where you asked it to be anyway - the window manager I'm using (an RHEL9-based Gnome manager) also does things like maximises the window if it's big enough (even if smaller than the actual maximum), so you are somewhat at the mercy of whatever policy the window manager is using to determine placement.

Slightly off topic:

I have noticed hiGetMaxScreenCoords() preserves the dimensions when the Virtuoso is invoked for first time and later it does not update the values. I noticed this when I invoke new Virtuoso in a smaller screen machine like laptop and then connect to a larger monitor, the hiGetMaxScreenCoords() returns the laptop screen coordinates.

RK56 said:

I have noticed hiGetMaxScreenCoords() preserves the dimensions when the Virtuoso is invoked for first time and later it does not update the values. I noticed this when I invoke new Virtuoso in a smaller screen machine like laptop and then connect to a larger monitor, the hiGetMaxScreenCoords() returns the laptop screen coordinates.

This has been this way as long as I can remember, but strangely enough I only found a relatively recent Cadence Change Request on this - CCR #2694574 . I vaguely recall talking with the R&D developer in the HI team about this in the past, but can't remember what he said... (and this CCR was filed after he retired). Anyway, you might want to contact customer support to get a duplicate filed on your behalf.

Note that hiGetMaxScreenCoords (having read up a bit) is supposed to give the maximum window size taking into account non-usable parts of the screen. There's hiGetScreenSize which returns the overall screen size in both pixels and millimetres. hiGetMaxScreenCoords also takes an optional argument (which can be set to t) which gives the overall size if you have multiple screens and also excludes some of the non-usable area.

Andrew

RK56 said:

I have noticed hiGetMaxScreenCoords() preserves the dimensions when the Virtuoso is invoked for first time and later it does not update the values. I noticed this when I invoke new Virtuoso in a smaller screen machine like laptop and then connect to a larger monitor, the hiGetMaxScreenCoords() returns the laptop screen coordinates.

This has been this way as long as I can remember, but strangely enough I only found a relatively recent Cadence Change Request on this - CCR #2694574 . I vaguely recall talking with the R&D developer in the HI team about this in the past, but can't remember what he said... (and this CCR was filed after he retired). Anyway, you might want to contact customer support to get a duplicate filed on your behalf.

Note that hiGetMaxScreenCoords (having read up a bit) is supposed to give the maximum window size taking into account non-usable parts of the screen. There's hiGetScreenSize which returns the overall screen size in both pixels and millimetres. hiGetMaxScreenCoords also takes an optional argument (which can be set to t) which gives the overall size if you have multiple screens and also excludes some of the non-usable area.

Andrew

Thanks for the info Andrew. I will file a CCR sooner