How to get rid of the "What's new" pop-up window on icfb

Hi,

despite I add the line

ddserv showWhat'sNew string "5.1"

in my .cdsenv, i am still getting the what's new window, when starting icfb.

I tried also

ddserv showWhatsNew string "5.1"

ddserv showWhatsNew string "no"
ddserv showWhatsNew string nil


It is not working.

Can anybody help me.

Thanks and best regard

Hannes

 

I have the following in my .cdsenv and don't get any whats new popups
in icfb or ADE

ddserv showWhatsNew string "5.1"
asimenv showWhatsNew string "5.1.0"

 

Hi,

I got rid of mine with using the following in .cdsenv of my home
directory:

ddserv showWhatsNew string "no"
layout showWhatsNew string "no"
asimenv showWhatsNew string "no"

You have to check which .cdsenv file is being used, since there is
priority between using .cdsenv of the current directory, home
directory and cadence installation default directory.
In my .....dfII/etc/tools/layout/.cdsenv file, the default command
uses:

layout showWhatsNew string "yes" nil

While the ddserve/.cdsenv file uses the line:
ddserv showWhatsNew string "yes" nil


Best regards,
I-FAB

 

When the pop up opens, in one of its pull down menus there is a "OFF
AT STARTUP" option. Click it and its gone.

 

Yeh, and this is saved e.g. in $HOME/.cdsenv which is NOT loaded by default
next time you start icfb/virtuoso. So there you are again ...

 

That depends one your settings for .cdsenv loading. If you are setup to load
using CSF, then the setup.loc file will control which .cdsenv files are loaded
and in which order.

If not setup for CSF, then the environment variable CDS_LOAD_ENV controls
which .cdsenv files are loaded. The default with no CSF and CDS_LOAD_ENV
not set is to load from the $HOME.

-Pete Zakel
()

"Got Mole problems?
Call Avogardo 6.02 x 10^23"

 

And here is the real problem: I don't like to save anything in my $HOME
directory (there are plenty of reasons for this), so

- CDS_LOAD_ENV is set to CWD
- but all "Off at Startup"s settings are written to $HOME/.cdsenv

A CDS_SAVE_ENV should be nice. If not set, then use CDS_LOAD_ENV and so on ...

PM

 

Actually, the saving through the env interface saves to the appropriate
place. The problem is that the adding of the showWhatsNew envvar setting
was not done through the env interface and was ignoring where the file was
actually loaded from when updating it.

I believe this is fixed in IC 6.1.4.

-Pete Zakel
()

"Don't feed the bats tonight."