IDBase_UI_Dialog::Destructor not always called when dialog exits?

Hi,
We're having an intermittent issue with one of our dialogs on CC 2014 on Mac 10.8. It's a Moveable Modal dialog and sometimes when it is closed, the next time it opens the dialog come up but IDialog::Open returns immediately rather than blocking as you would expect for a Modal dialog.
Having used the trace, what appears to be happening is that when the dialog is closed, when it works properly the last thing that InDesign does is:
DVModalDialogWindow::Destructor
DVWindow::ReleaseWindow deleting drover OS_Window for 3b50e600
IDBase_UI_Dialog::Destructor
but when it doesn't work, these three lines do not appear in the trace. Could we be doing something that would cause this?
Can anyone shed some light on this?
Thanks,
Dan Tate

I have found a workaround for this: when the IDialog::Open returns immediately, the IDialog::IsOpen returns true, so I can trap it. If I then call IDialog::SetDeleteOnClose(true) and then IDialog::Close, then the dialog does close properly and opens correctly the next time.
I'd still like to know why I am getting into this state in the first place though.
For further information, this seems to happen less frequently (if at all) on CC 2014 10.1, but happens fairly regularly on 10.0 - was anything changed in this area between the two versions?
Thanks,
Dan Tate

Similar Messages

Why is FmsDestroyFileAdaptor not being called when FMSCore exits

I'm developing a file-io plug-in and the FmsDestroyFileAdaptor or FmsDestroyFileAdaptor2 functions are not being called for my dll when the FMSCore process exits. I built the and tested the sample plug-in that comes with FMIS 3.5 and the same problem exists with it as well.
Any clues? Is this a bug?
Thanks,
George

This issue has been fixed in 3.5.2 release. See http://www.adobe.com/support/documentation/en/flashmediaserver/releasenotes.html

Listeners keyDown are not being called when keyDown in an popup l

For some reason the listeners titleWindow_keyDown are not being called when keyDown in an popup like so:
<?xml version="1.0" encoding="utf-8"?>
<s:SkinnablePopUpContainer xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx" width="400" height="300" keyDown="titleWindow_keyDown(event);" >
    <s:TitleWindow title="Edit Complaint" close="close()">
private function titleWindow_keyDown(evt:KeyboardEvent):void {
                    if (evt.charCode == Keyboard.ESCAPE) {
                        close();
Any ideas friends??

But in my code it is a child inside SkinnablePopUpContainer:
<s:SkinnablePopUpContainer xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx" width="400" height="300" keyDown="titleWindow_keyDown(event);" >
    <s:TitleWindow title="Edit Complaint" close="close()">

The HCM Review Budget Retro page level 2 scroll do not always refresh when scrolling thru level 1

When using the Review Budget Retro (Payroll for North America > Payroll Distribution > Commitment Accounting USA > Review Retro Distribution) page, scrolling thru level 1, level 2 does not always refresh. I am able to re-create this in our DMO environment. Has anyone else experienced this and resolved quickly on their own?

You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

Printer settings menu does not always change when switching printers

I am running OS 10.3.9 and also seen this issue on a 10.4 machine. When switching from one printer to another the printer options drop down menu does not always transfer to the correct menu for the newly selected printer. It stays at the menu for the last used printer. I am using several different Sharp printers as well as some HP models. The applications being used are Office 10 Word and Power Point. If anyone has seen this and has a fix I would greatly appreciate it.
Thanks

I don't have a solution but have also noticed that the printer in the menu is sort of like spinning the wheel of fortune.
Hopefully there is a solution but my guess is that it has something to do with a printer preference file that can get hijacked by different printers and applications.
I have noticed that a printer driver when installed will usually appear as the default printer even if it was not selected as such. I have also notice that different applications will do different things with different printers so I hope someone has a solution.

CommandButton actions not getting called when "disabled" element present

MyObjectForm.jsp contains commandButtons for "add", "update" and "delete" that are enabled/disabled according to the value of the bound id field.
MyObjectForm.jsp
<html>
<body>
<f:view>
<h:form id="create">
<h:inputHidden id="id" value="#{myObjectBean.id}" />
<h:panelGrid columns="3" border="0">
Name: <h:inputText id="name"
requiredMessage="*"
value="#{myObjectBean.name}"
required="true"/>
<h:message for="name"/>
// other fields
<h:commandButton id="add"
value="Add" disabled="#{myObjectBean.id!=0}"
action="#{myObjectBean.add}"/>
<h:commandButton id="update"
value="Update" disabled="#{myObjectBean.id==0}"
action="#{myObjectBean.update}"/>
<h:commandButton id="delete"
value="Delete" disabled="#{myObjectBean.id==0}"
action="#{myObjectBean.delete}"/>
<h:commandButton id="delete2"
value="Delete (no disabled element)"
action="#{myObjectBean.delete}"/>
</h:form>
</f:view>
</body>
</html>In its managed bean, MyObjectBean, if an id parameter is found in the request, the record is read from the database and the form is populated accordingly in an annotated @PostConstruct method:-
MyObjectBean.java
public class MyObjectBean {
private int id;
/** other properties removed for brevity **/
public MyObjectBean() {
LOG.debug("creating object!");
@PostConstruct
public void init() {
String paramId = FacesUtils.getRequestParameter("id");
if(paramId!=null && !paramId.equals("")){
getById(Integer.parseInt(paramId));
LOG.debug("init id:"+id);
}else{
public String delete(){
LOG.debug("delete:"+id);
MyObjectVO myObjectVO = new MyObjectVO();
ModelUtils.copyProperties(this, myObjectVO);
myObjectService.removeMyObjectVO(myObjectVO);
return "";
public String add(){
LOG.debug("add");
MyObjectVO myObjectVO = new MyObjectVO();
ModelUtils.copyProperties(this, myObjectVO);
myObjectService.insertMyObjectVO(myObjectVO);
return "";
public String update(){
LOG.debug("update:"+id);
MyObjectVO myObjectVO = new MyObjectVO();
ModelUtils.copyProperties(this, myObjectVO);
myObjectService.updateMyObjectVO(myObjectVO);
return "";
public void getById(int id){
MyObjectVO myObjectVO= myObjectService.findMyObjectById(id);
ModelUtils.copyProperties(myObjectVO, this);
/** property accessors removed for brevity **/
}When no parameter is passed, id is zero, MyObjectForm.jsp fields are empty with the "add" button enabled and the "update" and "delete" buttons disabled.
Completing the form and clicking the "add" button calls the add() method in MyObjectBean.java which inserts a record in the database. A navigation rule takes us to ViewAllMyObjects.jsp to view a list of all objects. Selecting an item from the ViewAllMyObjects.jsp list, adds the selected id to the request as a paramter and a navigation rule returns us to MyObjectForm.jsp, populated as expected. The "add" button is now disabled and the "update" and "delete" buttons are enabled (id is no longer equal to zero).
Action methods not getting called
This is the problem I come to the forum with: the action methods of commandButtons "update" and "delete" are not getting called.
I added an extra commandButton "delete2" to the form with no "disabled" element set and onclick its action method is called as expected:-
commandButton "delete2" (no disabled element) - works
<h:commandButton id="delete2"
value="Delete (no disabled element)"
action="#{myObjectBean.delete}"/>Why would "delete2" work but "delete", not?
commandButton "delete" (disabled when id is zero) - doesn't work
<h:commandButton id="delete"
value="Delete" disabled="#{myObjectBean.id==0}"
action="#{myObjectBean.delete}"/>The obvious difference is the "disabled" element present in one but not the other but neither render a disabled element in the generated html.
Am I missing something in my understanding of the JSF lifecycle? I really want to understand why this doesn't work.
Thanks in advance.
Edited by: petecknight on Jan 2, 2009 1:18 AM

Ah, I see (I think). Is the request-scoped MyObjectBean instantiated in the Update Models phase? If so then the id property will not be populated at the Apply Request Values phase which happens before this, making the commandButton's disabled attribute evaluate to true.
Confusingly for me, during the Render Response phase, the id property is+ set, so the expression is false (not disabled) giving the impression that the "enabled" buttons would work.
So, is this an flaw in my parameter passing and processing code or do you see a work around?

Even though I have ordered Firefox to clear my entire browsing history and cookies when it closes, it is not doing so when I exit. I have to manually clear the history and cookies each time.

I am running Firefox 10.0.2 for Linux, and have never had this problem with previous versions. I wonder if it is an issue of Firefox not quitting completely when I close it...meaning it would not clear the history and cookies because it is not technically shut down. This is just a theory, however. Any help would be appreciated!

Thanks for the suggestion. I made sure the prefs.js file had read and write permissions, and since then it seems to be saving my settings and deleting all the information I ordered it to on exit.
Thanks for your help! This was a minor problem, but it's nice to know that everything is working the way it's supposed to now.

My screen is not always responsive when I'm on a call

Most of the time when I'm on a call my END CALL or END + ANSWER button does not work. I'll push it over and over again and it just dims & come back like I never pushed it. I normally have to wait until the other person hangs up before I can click over or end a call. Has anyone else had this problem? I don't think my screen is that greasy or dirty.

Do you have a case on the phone? If so, then try removing the case and see if the phone works correctly with it removed. If it does, then there is something about the case that is blocking the proximity sensor. If it does not, you can try to reset the phone, holding the sleep/wake and home buttons together until you see the Apple logo and then release. See if it works after the phone restarts. If that doesn't help, the next step is a restore, first from a backup and if necessary as a new device. If it still doesn't work properly, then it could be hardware issue and the only way to check is to have Apple examine the phone.

In Unix, main JFrame focus not regained after modal dialog exit.

Hi all,
I'm new to this forum so hopefully this is the right place to put this question.
I have a relatively simple GUI application written in Java 6u20 that involves a main gui window (extends JFrame). Most of the file menu operations result in a modal dialog (either JFileChooser or JOptionPane) being presented to the user.
The problem is that when running on Unix (HPUX), the process of changing focus to one of these modal dialogs occasionally results in a quick flash of the background terminal window (not necessarily that used to launch the Java), and the process of closing the modal dialogs (by any means, i.e. any dialog button or hitting esc) doesn't always return focus to the main extended JFrame object, sometimes it goes to the terminal window and sometimes just flashes the terminal window before returning to the main JFrame window.
I think the problem is with the Unix window manager deciding that the main focus should be a terminal window, not my Java application, since the problem occurs in both directions (i.e. focus from main JFrame to modal dialog or vice versa).
In most cases of JOptionPane, I DO specify that the main extended JFrame object is the parent.
I've tried multiple things since the problem first occured, including multiple calls to a method which calls the following:
.toFront();
.requestFocus();
.setAlwaysOnTop(true);
.setVisible(true);
..on the main JFrame window (referred to as a public static object)...
just before and after dialog display, and following selection of any button from the dialogs. This reduced the frequency of the problem, but it always tends to flash the terminal window if not return focus to it completely, and when it occurs (or starts to occur then gets worse) is apparently random! (which makes me think it's an OS issue)
Any help appreciated thanks,
Simon
Self-contained compilable example below which has the same behaviour, but note that the problem DOESN'T occur running on Windows (XP) and that my actual program doesn't use auto-generated code generated by a guibuilder:
* To change this template, choose Tools | Templates
* and open the template in the editor.
package example;
import javax.swing.JOptionPane;
* @author swg
public class Main {
     * @param args the command line arguments
    public static void main(String[] args) {
        java.awt.EventQueue.invokeLater(new Runnable() {
            public void run() {
                new NewJFrame().setVisible(true);
class NewJFrame extends javax.swing.JFrame {
    /** Creates new form NewJFrame */
    public NewJFrame() {
        initComponents();
    /** This method is called from within the constructor to
     * initialize the form.
     * WARNING: Do NOT modify this code. The content of this method is
     * always regenerated by the Form Editor.
    @SuppressWarnings("unchecked")
    // <editor-fold defaultstate="collapsed" desc="Generated Code">
    private void initComponents() {
        jMenuBar1 = new javax.swing.JMenuBar();
        jMenu1 = new javax.swing.JMenu();
        jMenuItem1 = new javax.swing.JMenuItem();
        jMenu2 = new javax.swing.JMenu();
        setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
        jMenu1.setText("File");
        jMenuItem1.setText("jMenuItem1");
        jMenuItem1.addActionListener(new java.awt.event.ActionListener() {
            public void actionPerformed(java.awt.event.ActionEvent evt) {
                jMenuItem1ActionPerformed(evt);
        jMenu1.add(jMenuItem1);
        jMenuBar1.add(jMenu1);
        jMenu2.setText("Edit");
        jMenuBar1.add(jMenu2);
        setJMenuBar(jMenuBar1);
        javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());
        getContentPane().setLayout(layout);
        layout.setHorizontalGroup(
            layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addGap(0, 400, Short.MAX_VALUE)
        layout.setVerticalGroup(
            layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
            .addGap(0, 279, Short.MAX_VALUE)
        pack();
    }// </editor-fold>
    private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) {
        int result = JOptionPane.showConfirmDialog(this, "hello");
    // Variables declaration - do not modify
    private javax.swing.JMenu jMenu1;
    private javax.swing.JMenu jMenu2;
    private javax.swing.JMenuBar jMenuBar1;
    private javax.swing.JMenuItem jMenuItem1;
    // End of variables declaration
}

It won't comfort you much, but I had similar problems on Solaris 10, and at the time we traked them down to a known bug [6262392|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6262392]. The status of this latter is "Closed, will not fix", although it is not explained why...
It's probably because the entry is itself related to another, more general, bug [6888200|http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=b6eea0fca217effffffffe82413c8a9fce16?bug_id=6888200], which is still open.
So it is unclear whether this problem will be worked upon (I suspect that yes) and when (I suspect that... not too soon, as it's been dormant for several years!).
None of our attempts (+toFront(...)+ etc...) solved the issue either, and they only moderately lowered the frequency of occurrence.
I left the project since then, but I was said that the workaround mentioned in the first bug entry (see comments) doesn't work, whereas switching to Java Desktop instead of CDE reduced the frequency of the issues (without fixing them completely either) - I don't know whether it's an option on HPUX.
Edited by: jduprez on Jul 9, 2010 11:29 AM

Making sure a function is always called when a vi is closed/aborted

Hello all,
Maybe a simple question for the LV gurus out there but I'm struggling with this.
I have a camera that I'm controlling via a functional global.
When I call the different functions everything works as expected as long as I make sure that the "exit camera" function is called as the last function. (which is normal)
If I do not call the "exit camera" function as last function (ie a user closed the vi with an abort or some critical error occured inside the code), it seems like the DLL keeps a handle open and I cannot access the camera anymore until I close down LabVIEW and I physically unplug the device from my system. When I plug it back in I can again use my camera normally.
Is there a way in LabVIEW that I can keep track of my camera to determine if it is still being used or not and correctly close it when nobody is using it anymore.
I guess with OO mechanisms it should be possible but since I've never used OO before with LabVIEW I was wondering if there was an alternative solution/mechanism/example I could look at.....
Thanks for all the help and suggestions!
Kirsten
PS: I know I can disable the 'abort' button from the VI ... I'm not looking for that answer

k_tunsten wrote:
If I do not call the "exit camera" function as last function (ie a user closed the vi with an abort or some critical error occured inside the code), it seems like the DLL keeps a handle open and I cannot access the camera anymore until I close down LabVIEW and I physically unplug the device from my system. When I plug it back in I can again use my camera normally.
Well, the VI knows if there is an error, so the code can take appropriate action if that occurs using proper error handling.
To deal with the user closing the VI, use a "panel close?" filtering event, discard it, exit the camera, then close the VI once everything is cleaned up..
LabVIEW Champion . Do more with less code and in less time .

Performance counters are not always removed when APM is disabled

On several occasions I've noticed that even after:
removing a server from the target group of all APM management packs
waiting until IISReset is required
doing the IISReset
still some .NET APPS performance counters linger on or maybe gets recreated when load (out of my control) hits the server.
Profiling the IIS process using Visual Studio I see no use of PerfMon64, so I looks like APM is disabled on the server, but why isn't the performance counter(s) gone?
Thanks
Michael Brandt Lassen

Michael,
The performance counters category ".NET Apps" is registered on the server at the moment of the APM agent installation (part of MMA agent). Later, the instances are created by the monitored applications. If no applications are monitored, then no
instances are registered inside the category but category itself isn't going away from the server while APM/MMA is still installed.
I think it's done to only care about instance creation from inside of the monitored app but not about the category registration from within the app (which requires more privileges...). Also, APM service can always monitor the existing category to wait for
the new instances and avoid checking for the category itself to re-register the PDH queries..
It's easy to kill this category even if MMA agent is installed but it might easily break the monitoring scenarios if some app will be monitored on this server again... (E.g. you can run "unlodctr" and point it to the appropriate counters dll or
ini file...). So, it's better to keep it as is.
Dmitry Matveev

Shutdown hook not getting called when running tomcat as a service

I have a shutdown hook as part of a lifecycle <Listener> tomcat6 class, which gets created and registered in the class's constructor (class is referenced in the server.xml). The hook gets called during shutdown when tomcat has been started from a shell, but not when tomcat has been installed as a service. The -Xrs flag doesn't make a difference either way. I am running java 6u12 server VM (haven't tried client) and prior versions. Does anyone have any ideas? This has been tested by starting/stopping from the Control Panel, and also with 'tomcat6 //TS/ServiceName' (i.e. in test mode)
One possibility is that tomcat internally calls Runtime.halt(), but the shutdown process appears to be normal and the same with either scenario. The other possibility is that the JVM has an issue. The tomcat user groups don't have anything to offer.
Thoughts?
tia

sanokistoka wrote:
jschell wrote:
sanokistoka wrote:
Let me ask the last question in a better way: Does anyone have any GOOD ideas?Get back to us when you have found your good solution.Stop wasting bandwidth. I didn't post here to be a smart ars like you and pretend that I have a solution to a rare problem... FYI - the workaround is to use the tomcat lifecycle events (AFTER_STOP_EVENT) to achieve the same - why do you think I mentioned it's a tomcat listener in the first place? Feel free to educate me.
So you are claiming that Runtime.getRuntime().addShutdownHook() that you posted in the above is not part of the java API?
Or perhaps that everything that is added via addShutdownHook() runs?
Surely you are not claiming that it isn't calling addShutdownHook() in the first place?
Get a life and a job.I have both but thanks for the concern.
sanokistoka wrote:
swamyv wrote:
There are free tools available to debug windows. I think gdb is one of them. If you search you can find some good tools.
If you find any good tools that you like share it with us.
Yes I will try gdb (have cygwin) and see where this takes us - not sure if the JVM or tomcat6.exe have the symbols to get a meaningful stack trace. As luck would have it, [https://issues.apache.org/bugzilla/show_bug.cgi?id=10565|https://issues.apache.org/bugzilla/show_bug.cgi?id=10565] claims that "shutdown hooks are not supported in a container environment" although there is no such restriction in the servlet spec, which would make this a tomcat issue (it does sound like that tomcat6.exe wrapper is somehow involved). Unfortunately, tomcat does NOT issue the AFTER_STOP_EVENT if killed before it has completed its start-up (it appears its own shutdown hook, which sends the event, is not registered until it has fully come up); thus the need for a shutdown hook (at least, up until it's fully up). A shutdown hook is still required in my case for clean-up after tomcat is completely out of the picture. It sounds like the proper architecture here is to really embed tomcat in an application, and create a shutdown hook at the outer level.
Educate me some more. The above description certainly seems like you are suggesting that both of the following are true.
1. It is not a bug in the VM.
2. The problem, for your implementation, is in how the wrapper terminates the windows service.
Perhaps what is actually happening it that addShutdownHook() is never being called at all? Thus of course any processing of the thread associated with that would never, ever run.
And that happens because you are banging on the stop service so fast that it doesn't actually have time to spin up?

TM drive does not always mount when reconnected

Forgive me if this has been covered, but I could not find it in the archive.
I am using a Fantom 500GB drive for backup from my laptop. Every few days, when I reconnect the drive, it will not mount and backups will not happen. The drive is both Firewire and USB - I generally use Firewire. I have tried repowering the drive, unplugging and reconnecting in all the various permutations, and the drive will not mount. The two things that will make it mount are 1) reboot the computer, or 2) connect the USB cable (although, the Firewire will still not work until after a reboot). Any ideas?
Thanks,
Andy

Andy,
I was just reading some reviews on Newegg dot com for the Fantom Titanium-II TFD500U16 500GB 7200 RPM 16MB Cache USB 2.0 External Hard Drive which I presume is the one you have purchased. There are a lot of negative reviews which suggests that it should be avoided. Read them for yourself.
You get what you pay for and for my hard earn dollar I would be wanting a reliable interface and a reliable mechanism. Seems to me that one or both of those are not up to scratch in your case. There are a lot of good quality Firewire/USB devices on the market such as those from OWC aka Other World Computing. Spend the dollars and buy quality and you wont regret it. You have the best computer on the market with the best OS so pamper it a bit.
Cheers
Chris

ItemStateChanged not always called in ComboboxEditor

Hi all,
I have implemented a custom JTable Cell editor which extends AbstractCellEditor. Most of the time everything works fine but sometimes when I add new rows to the table and then attempt to make a new selection in the combobox I cannot. When I drop down the combo and select something itemStateChanged is not fired. Its only for the new row. The combobox in the other rows continues to work. HOWEVER, if I dropdown the combo, and hold the mouse button down and move it over the desired item and release the mouse button itemstateChanged IS fired and the selection is made??????? My editor includes the following method implementations.
/** Creates a new instance of oaJComboBoxTableEditor */
public oaJComboBoxTableEditor() {
_combo = new oaJComboBox();
_combo.getEditor().getEditorComponent().addKeyListener(this);
_combo.getEditor().getEditorComponent().addFocusListener(this);
_combo.addFocusListener(this);
_combo.addItemListener(this);
_combo.addPopupMenuListener(this);
public boolean startCellEditing(EventObject anEvent) {
System.out.println("startCellEditing");
_combo.addItemListener(this);
_combo.addPopupMenuListener(this);
return true;
public void focusGained(FocusEvent e) {
System.out.println("oaJComboboxTableEditor::focusGained");
_combo.addItemListener(this);
_combo.addPopupMenuListener(this);
startCellEditing(new EventObject(this));
public void focusLost(FocusEvent e) {
System.out.println("oaJComboboxTableEditor::focusLost");
stopCellEditing();
public void popupMenuWillBecomeInvisible(PopupMenuEvent e) {
System.out.println("oaJComboboxTableEditor::popupMenuWillBecomeInvisible");
// need this to let the popup close gracefully
SwingUtilities.invokeLater(new Runnable() {
public void run() {
stopCellEditing();
public boolean stopCellEditing() {
_combo.removeItemListener(this);
_combo.removePopupMenuListener(this);
fireEditingStopped();
return true;
}

See my offer at the link shown below:
http://forum.java.sun.com/thread.jsp?forum=57&thread=408335
;o)
V.V.

Wifi not always on when computer turned on

Every now and then when I turn on my late 2008 macbook the wifi doesn't show any bars, I try to turn wifi on but nothing happens so I restart my computer and everything works fine. It happens every 5-6 times I turn it on. Anyone know why?

Hello @cjackson8769,
I understand that the power indicator light on your power supply is on, but you are not able to boot your HP Pavilion Slimline s3700y Desktop PC. I am providing you with an HP Support document: Troubleshooting Power Supply Issues, which will walk you through troubleshooting the issue you are experiencing and provide you with a solution.
Please follow the steps contained within the document and re-post if you require additional support. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

IDBase_UI_Dialog::Destructor not always called when dialog exits?

Similar Messages

Maybe you are looking for