browse files

S

stroller

Guest
hi, i'd really like to have a browse widget on my skill forms to enable
a user to point at the unix dir he wants to deposit all the files i'm
exporting as part of a custom mixed-signal methodology. i can't seem to
find a public function for this though, am i just missing this in the
manual or did cadence choose not to make this a public function?

thx
 
On 15 Nov 2005 11:39:36 -0800, "stroller" <smcbutler@hotmail.com> wrote:

hi, i'd really like to have a browse widget on my skill forms to enable
a user to point at the unix dir he wants to deposit all the files i'm
exporting as part of a custom mixed-signal methodology. i can't seem to
find a public function for this though, am i just missing this in the
manual or did cadence choose not to make this a public function?

thx
The reason is that there is no common file browser until ICOA5251 - I think the
function there is something like hiDisplayFileDialog() - I've only done a quick
search... there are several related functions - and these are covered in the
User Interface SKILL Functions manual.

With the move to Qt based widgets, it was about time we did this.

Before now, some applications have developed their own browsers, but there was
no central file browser.

Regards,

Andrew.
 
In article <1imkn11apmcu83mu2f7trn667do15n5gin@4ax.com>,
andrewb@DcEaLdEeTnEcTe.HcIoSm says...
With the move to Qt based widgets, it was about time we did this.
After reading this sentence I had to rub my eyes and do some searching
on the web on Cadence and Qt without very much luck.

We use IC51 currently so excuse me if there is something in the newer
releases that I have missed.

When will we see ADE in QT?
--
Svenn
 
On Wed, 16 Nov 2005 09:16:12 +0100, Svenn Are Bjerkem <svenn.are@bjerkem.de>
wrote:

In article <1imkn11apmcu83mu2f7trn667do15n5gin@4ax.com>,
andrewb@DcEaLdEeTnEcTe.HcIoSm says...
With the move to Qt based widgets, it was about time we did this.

After reading this sentence I had to rub my eyes and do some searching
on the web on Cadence and Qt without very much luck.

We use IC51 currently so excuse me if there is something in the newer
releases that I have missed.

When will we see ADE in QT?
ICOA5251, not IC5141. The whole of DFII (well, most of it; there's the odd thing
here and there that still uses Motif) is in Qt since ICOA5251 - although there
is not much taking advantage of this in ICOA5251 - that's coming later. Existing
"hi" based forms now use underlying Qt widgets instead of underlying Motif
widgets.

So you'll see some changes in the look and feel (e.g. tear-off menus, buttons at
bottoms of forms instead of the top, some ability to apply styles to alter the
appearance of the widgets) - but the bigger changes are due next year.

Andrew.
 
So, what are the bigger changes? :)

Andrew Beckett wrote:
On Wed, 16 Nov 2005 09:16:12 +0100, Svenn Are Bjerkem <svenn.are@bjerkem.de
wrote:


In article <1imkn11apmcu83mu2f7trn667do15n5gin@4ax.com>,
andrewb@DcEaLdEeTnEcTe.HcIoSm says...

With the move to Qt based widgets, it was about time we did this.

After reading this sentence I had to rub my eyes and do some searching
on the web on Cadence and Qt without very much luck.

We use IC51 currently so excuse me if there is something in the newer
releases that I have missed.

When will we see ADE in QT?


ICOA5251, not IC5141. The whole of DFII (well, most of it; there's the odd thing
here and there that still uses Motif) is in Qt since ICOA5251 - although there
is not much taking advantage of this in ICOA5251 - that's coming later. Existing
"hi" based forms now use underlying Qt widgets instead of underlying Motif
widgets.

So you'll see some changes in the look and feel (e.g. tear-off menus, buttons at
bottoms of forms instead of the top, some ability to apply styles to alter the
appearance of the widgets) - but the bigger changes are due next year.

Andrew.
 

Welcome to EDABoard.com

Sponsor

Back
Top