Skip to main content
Z
ZS_103838891-Visitor
1-Visitor
September 6, 2022
Question

Access the UI components after placement them in the navigation pane

  • September 6, 2022
  • 1 reply
  • 2278 views

Hello all, your help is needed again.

 

I built a new pane using function ProNavigatorpanePHolderAdd(), which adds a layout from resource file as expected.

Q#1: How do I make this pane active immediately, without clicking on the pane tab?

Q#2 Do I need to activate this layout before trying to access UI components?

 

In order to access UI, e.g. close push button from a new pane I do the following:

- define listener class 

class CommitClosePushButtonListener : public uifcDefaultPushButtonListener
{
public:
    CommitClosePushButtonListener() {}
   ~CommitClosePushButtonListener() {}

   void OnActivate(uifcPushButton_ptr handle);
};

- activate it

   ProNavigatorpanePHolderComponentnameGet(pane_name, "CommitCloseBTN",       &component_name);

   uifcPushButton_ptr commitClose = uifcPushButtonFind(layout_name, component_name);

   CommitClosePushButtonListener* commitCloseLis = new CommitClosePushButtonListener();
   commitClose->AddActionListener(commitCloseLis);
   

- define action callback

void CommitClosePushButtonListener::OnActivate(uifcPushButton_ptr handle)
{
   //debug print
   ProTKFprintf(logfile1, "PushButton\n");
}

Q#3: Why on testing this button I don't get the debug print?

 

Many thanks for your answers.  

 

1 reply

Z
ZS_103838891-VisitorAuthor
1-Visitor
September 7, 2022

UPD.

I found bug in my code.

     uifcPushButton_ptr commitClose = uifcPushButtonFind(layout_name, component_name);

should be instead

    uifcPushButton_ptr commitClose = uifcPushButtonFind(current_window_device_name, component_name);

 

I am left with single question:

   Q#1: How do I make this pane active immediately, without clicking on the pane tab?

 

If somebody knows?

Thank you.

 

    E
    Eike_Hauptmann15-Moonstone
    15-Moonstone
    September 7, 2022

    I do it by async. mapkey. So simply load an async mapkey for the current window the navigator pane is created in.

     

     Another way would be to find the parent component until you get the tabcontainer and tell it to switch to your tab. But I think that would be much more complex and changes in the std. Dialog from Creo are much more likely to affect your Utility in a way that can cause crashes and that kind of stuff. So the easiest way should be to place a mapkey on the mapkey stack.

     

    Also there are some config options that can cause different behaviors that you need to think of. You can undock the tree from die Creo standard dialog and this affects your navigator pane, too.

     

    Br,

    Eike

      Z
      ZS_103838891-VisitorAuthor
      1-Visitor
      September 7, 2022

      Eike, thanks a lot. I will look at the mapkey solution. Is it part from OTK?

      Terms & ConditionsAccessibility statement