Invalid control ID

[winter1970]

in my project, i have two uirs: main.uir, list.uir

when i click the menu "list" of main.uir, it will load list.uir.

in list.uir, i place an Command control, its callback function is test()

in fucntion test()，i have three lines codes below:

----------------------------------------------

GetCtrlAttribute(panel,PANELLIST_RINGSLIDE,ATTR_VISIBLE,&tempVar); //Retrieve
 if(tempVar)
SetCtrlAttribute(panel,PANELLIST_RINGSLIDE,ATTR_VISIBLE,0); //Hide

-------------------------------------------------

the RINGSLIDE control is in list.uir,and the headfile list.h also have the PANELLIST_RINGSLIDE define :

#define PANELLIST_RINGSLIDE 12 /* control type: slide, callback function: (none) */

....

But,

in Debug mode, when i close the panel of list.uir, the error appearence：

NON-FATAL RUN-TIME ERROR: "mainPanel.c", line 2229, col 5, thread id 0x00001774: Library function error (return value == -13 [0xfffffff3]). Invalid control ID

the error line is:

GetCtrlAttribute(panel,PANELLIST_RINGSLIDE,ATTR_VISIBLE,&tempVar); //Retrieve

And,

in Release mode, everthing is ok.

Bug?

[RobertoBozzolo · Accepted solution]

Looks like you are not limiting the callback at the EVENT_COMMIT event: can you post the complete control callback code?

Since it is a non fatal error the executable does not report it.

[winter1970]

to RobertoBozzolo

you are right. thank you!

when i use return 1 ,it is ok now .

[RobertoBozzolo]

Returning 1 from a control callback means to swallow the event, i.e. prevent it to be passed along to other processing routines. It should be used cautiously, I remember to have used it only a few times in several years.

It probably isn't the solution to your problems but it possibly masks it under some circumstances.

Can you post the complete callback code? I'd like to understand if and how this can be an acceptable fix or not.

[winter1970]

---

@RobertoBozzolo  已写:

Returning 1 from a control callback means to swallow the event, i.e. prevent it to be passed along to other processing routines. It should be used cautiously, I remember to have used it only a few times in several years.

It probably isn't the solution to your problems but it possibly masks it under some circumstances.

Can you post the complete callback code? I'd like to understand if and how this can be an acceptable fix or not.

---

To RobertoBozzolo:

i dont know how to send the project to you,so i post some screenshot here.

[RobertoBozzolo]

I was not intending to have the complete project, but simply to copy/paste the callback code here.

I cannot understand from the screenshots what is happening, but you are probably getting some error on EVENT_CLOSE event so that he code jumps to Error: and then Error_free: labels trying to address a control that has already been discarded: you should debug this condition to clear the code in order to prevent such a condition.

As a side note, I see that you are calling RunUserInterface () when showing the popup panel: this is not necessary and should be avoided since one RunUserInterface () is enough at code start to handle all the panels you may load and display during program life.

[winter1970]

---

@RobertoBozzolo  已写:

I was not intending to have the complete project, but simply to copy/paste the callback code here.

I cannot understand from the screenshots what is happening, but you are probably getting some error on EVENT_CLOSE event so that he code jumps to Error: and then Error_free: labels trying to address a control that has already been discarded: you should debug this condition to clear the code in order to prevent such a condition.

As a side note, I see that you are calling RunUserInterface () when showing the popup panel: this is not necessary and should be avoided since one RunUserInterface () is enough at code start to handle all the panels you may load and display during program life.

---

i remove the "RunUserInterface ()" ,but found the panel appear,and immediately disappear。so cannot remove "RunUserInterface ()".

-------------------------------------------------

and ,i add  the statements :

"default: return 0; " in switch case，and found the error disappear,it is ok now.

But，i don't know why it is so.

[RobertoBozzolo]

---

@winter1970  ha scritto:

---

...cannot remove "RunUserInterface ()".

---

That's because you have a RemovePopup immediately after RunUserInterface ()!

You should:

- Remove RunUserInterface, RemovePopup and DiscardPanel from MergeExcel () function

- Add DiscardPanel instead of QuitUserInterface in QuitMergePanel

The underlying principle is that you can show a panel as a popup, let the unique RunUserInterface called at program start handle panel events and have on the panel a control that discards it.