• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Virtuoso, ADE etc. windows open on wrong display

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 18319
  • Members are here 0
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

Virtuoso, ADE etc. windows open on wrong display

itos
itos over 10 years ago

Hi,


Virtuoso, ADE etc. seems to open all windows on the left side!

I usually have two monitors with the primary monitor on the right and the secondary monitor on the left. Now Cadence opens all windows on my secondary monitor and I always need to drag them manually back to my primary monitor on the right.

Is there an option that Cadence just opens its windows on the same monitor?

Thanks

itos

EDIT: I use X-forwarding and/or xpra on Windows, so I do not access Cadence locally on a Linux box

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    There are some cdsenv settings for each of the tools to specify the default coordinates where windows are placed - so you could set those (I can't remember what they are called off the top of my head, and don't have the software handy).

    There's no real knowledge of multiple monitors in Virtuoso, so you can't really control it that way.

    Some X window managers give some level of control over window placement, but this is very dependent upon the window manager and also whether an application requests a specific coordinate position.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • analogy
    analogy over 10 years ago

    The problem with any X-Terminal is that they save the last state of window position when open.Usually you have to clear session buffers.In your case, it would be great if you switch to Xming, their release after 2013 has probably fixed this issue (the last time I used it was a long while back).If you have OS-X, there is an option on dashboard itself to define default monitor for opening Xming windows.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago
    I don't think this is true - most tools do not retain their window positions between separate invocations of the tool (at least not in my experience - maybe some window managers do).
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • analogy
    analogy over 10 years ago

    Correction : The problem with any Few X-Terminal applications save last state of window position when invoked for the first time.When a user logs off from the Xterm session, he/she might expect to have window positions at the same place that was saved during last session (Xterm control sequence P s = 1 3).

    But yeah, Andrew is right, about separate invocations in most tools, very few tools have windows position state function.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • itos
    itos over 10 years ago

    Hi Andrew, Thanks. Do you have a pointer to the correct options? I tried using a couple of things including:

    envSetVal("asimenv.window" "x" 'int 1024)

    hiGetCIWindow()->formRelativeTo = "currentWindow"
    hiGetCIWindow()->optionFormRelativeTo = "currentWindow"

    hiGetCIWindow()->formPlacement = "right"
    hiGetCIWindow()->optionFormPlacement = "right"

    hiSetDBoxDefaultLocation(1921:1)
    hiSetFormPosition(1921:1)

    None of these things changed just a little bit. It's frustrating. The problem is that I can't really put my secondary monitor to the right hand side because it is essentially a tablet where I write on ...

    Regarding saving window positions: It does not seem they are saved for me. The library manager merely opens on random positions when I move the window and close it. When I do nothing, it always opens at (0,0) on my secondary monitor ...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Those settings are for forms and dialog boxes, not windows.

    You can use these ~/.cdsenv settings:

    layout leWindowBBox string "((120 185) (1020 875))"
    schematic schWindowBBox string "((120 185) (1020 875))"
    schematic symWindowBBox string "((120 185) (1020 875))"

    For the library manager, these settings or similar can be placed in ~/.libmgr :

    cdsLibManager.x: 200
    cdsLibManager.y: 186
    cdsLibManager.width: 925
    cdsLibManager.height: 711

    For the "browse" button on forms, these can be place din ~/.libsel

    cdsLibSelect.x: 986
    cdsLibSelect.y: 104
    cdsLibSelect.width: 925
    cdsLibSelect.height: 580

    Library manager and library select will remember their settings from last time though.

    If these don't help, please contact customer support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • itos
    itos over 10 years ago

    Hi Andrew,


    Thanks for the detailed lines!

    Incredible, still ignored, so frustrating.

    Actually, it also seems to me that the placement is non-deterministic: Windows are placed arbitrarily.

    Neither is it the last position, nor always the same.

    It's just 80% of the time the left most monitor. :-(

    itos

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago
    This may be something to do with the X server or Window Manager you're using... what are they?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • itos
    itos over 10 years ago

    It's xpra (alternatively just the Cygwin X server).

    However, it seems that Cadence requests these weird numbers. It's written directly in the window messages (see http://xpra.org/trac/ticket/811).

    Since the placement is really arbitrary (neither the last position, nor whatever I put into the config files) it really seems to me Cadence uses a random generator to make the behavior as non-deterministic as possible :-(

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information