Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 14218
  • 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

Perl TK

Khurana

Hi,

I am calling a perl (TK) script using a menu pick inside a tool and the TK dialog pops up fine the first time the perl TK script is invoked after launching the tool, but subsequent invocations of the script do not pop up the TK window - any ideas as to what may be causing this

Here's the script:

#!/usr/bin/perl
use strict;
use warnings;
use Tk;

my $mw = MainWindow->new;
$mw->title("Hello World");
$mw->Button(-text => "Exit", -command => sub {exit})->pack;
MainLoop;

Thanks,
Varun

Parents

  • Hi Varun,

    Please accept my apologies if you were offended by my post or found it impolite. That was not my intention - I was trying to encourage you (and others) that by giving enough details you stand a much greater chance of getting an answer to your problem. I respond to posts on a completely voluntary basis in my free time - it is not part of my job at Cadence to do this. So I have to try to balance my time and so I am much more likely to spend time answering those where sufficient information has been provided. I dislike leaving any questions unanswered if others have not responded (see the amount of posts I have made) - but of course it's best for me personally if I don't have to go back and forth several times, especially when I'm often travelling and may be unable to respond for a few days.

    Anyway, that was not meant to be an excuse, and my previous response was not mean to be a lecture.

    If you can enlighten me as to precisely how you're  invoking the Perl/Tk application, which version of Virtuoso you're using and so on, it would really help. Maybe we can get to the bottom of the problem.

    I did just try using:

    id=ipcBeginProcess("perlGUI")

    id2=ipcBeginProcess("perlGUI")

    And I get two on the screen. If I use ipcIsAliveProcess(id) or ipcIsAliveProcess(id2) I get t, until I've hit the Exit button on the "perlGUI" program - at which point the ipcIsAliveProcess(id) etc returns nil, as I'd expect.

    I'm running using IC614 (6.1.4.500.8) - although I'd be surprised if that makes a difference.

    Having exited, I can run again and a new one will get launched.

    Regards,

    Andrew.

Reply

  • Hi Varun,

    Please accept my apologies if you were offended by my post or found it impolite. That was not my intention - I was trying to encourage you (and others) that by giving enough details you stand a much greater chance of getting an answer to your problem. I respond to posts on a completely voluntary basis in my free time - it is not part of my job at Cadence to do this. So I have to try to balance my time and so I am much more likely to spend time answering those where sufficient information has been provided. I dislike leaving any questions unanswered if others have not responded (see the amount of posts I have made) - but of course it's best for me personally if I don't have to go back and forth several times, especially when I'm often travelling and may be unable to respond for a few days.

    Anyway, that was not meant to be an excuse, and my previous response was not mean to be a lecture.

    If you can enlighten me as to precisely how you're  invoking the Perl/Tk application, which version of Virtuoso you're using and so on, it would really help. Maybe we can get to the bottom of the problem.

    I did just try using:

    id=ipcBeginProcess("perlGUI")

    id2=ipcBeginProcess("perlGUI")

    And I get two on the screen. If I use ipcIsAliveProcess(id) or ipcIsAliveProcess(id2) I get t, until I've hit the Exit button on the "perlGUI" program - at which point the ipcIsAliveProcess(id) etc returns nil, as I'd expect.

    I'm running using IC614 (6.1.4.500.8) - although I'd be surprised if that makes a difference.

    Having exited, I can run again and a new one will get launched.

    Regards,

    Andrew.

Children
No Data

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.