java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
ConsultComm-3.0.5
The timeout plugin will not work. It has been activated via Menu -> Tool -> Manage Plugins -> select timer button by checking Use Plugin?. However, the timeout never kicks in. Have attempted to adjust the timeout for various times, have selected both Pause after idle and switch to project, but it still does not detect the idle time.
Other noted behavior while configuring TimeOut plugin:
- when initially activating (checking Use Plugin? checkbox), the other attributes (Perform action , etc) are not enabled for setting you must save and then go back in to set as desired.
- If Switch to project is selected idle action, the specified project is not repopulated when one goes back into the settings (the project is saved to TimeOut.xml, but the drop down box is not properly reset upon reentry).
- After going in and out of Plugin settings several times, the basic timer functionality will not work when started (I have a project selected). The animation will work, but the timer does not increment? Closing ConsultComm window and reopening rectifies the problem (sorry, but I cannot consistently recreate).
Note: Other configuration settings:
- do not have JDBC setup
- not using skins/themes
- General Preferences: show time in seconds, save info every 30 seconds, show animated icons is checked
Any suggestions about how to debug the idletime?
New to Java, is there an way to activate the Java console while running ConsultComm so I can see what is happening or even better is there a debugger that I can activate?
Much thanks,
Tim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yup, the Win32 idle time plugin is broken. Sorry 'bout that...
I fixed it in CVS, but haven't done a formal release of the fixes yet. These bugs will be resolved in the upcoming 3.1 release candidate which should be out later on this weekend. So you should have fixes for the above issues in a few days!
The explanation as to why it is broken (these issues are fixed in the upcoming release):
This plugin was written by someone else, and I'm finding the user interface is pretty buggy. I'll probably end up re-writing it, but most of the settings will stick of you make a selection, save it, then restart ConsultComm. The bug of selecting "Use Plugin" and then not enabling the options to configure the plugin will also go away if you exit out and go back in.
The timer bug is due to the way Windows handles .dll's. Since Java doesn't have a way of detecting how long a user is idle, I had to write some native Win32 code to do so. It works as long as you don't reload the plugin... which happens every time you configure ConsultComm. So as long as you don't make any configuration changes, the plugin should work.
I'll close this out once we verify the release candidate works for you. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
XP Pro SP1 running with administrator privileges
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
ConsultComm-3.0.5
The timeout plugin will not work. It has been activated via Menu -> Tool -> Manage Plugins -> select timer button by checking Use Plugin?. However, the timeout never kicks in. Have attempted to adjust the timeout for various times, have selected both Pause after idle and switch to project, but it still does not detect the idle time.
Other noted behavior while configuring TimeOut plugin:
- when initially activating (checking Use Plugin? checkbox), the other attributes (Perform action , etc) are not enabled for setting you must save and then go back in to set as desired.
- If Switch to project is selected idle action, the specified project is not repopulated when one goes back into the settings (the project is saved to TimeOut.xml, but the drop down box is not properly reset upon reentry).
- After going in and out of Plugin settings several times, the basic timer functionality will not work when started (I have a project selected). The animation will work, but the timer does not increment? Closing ConsultComm window and reopening rectifies the problem (sorry, but I cannot consistently recreate).
Note: Other configuration settings:
- do not have JDBC setup
- not using skins/themes
- General Preferences: show time in seconds, save info every 30 seconds, show animated icons is checked
Any suggestions about how to debug the idletime?
New to Java, is there an way to activate the Java console while running ConsultComm so I can see what is happening or even better is there a debugger that I can activate?
Much thanks,
Tim
Yup, the Win32 idle time plugin is broken. Sorry 'bout that...
I fixed it in CVS, but haven't done a formal release of the fixes yet. These bugs will be resolved in the upcoming 3.1 release candidate which should be out later on this weekend. So you should have fixes for the above issues in a few days!
The explanation as to why it is broken (these issues are fixed in the upcoming release):
This plugin was written by someone else, and I'm finding the user interface is pretty buggy. I'll probably end up re-writing it, but most of the settings will stick of you make a selection, save it, then restart ConsultComm. The bug of selecting "Use Plugin" and then not enabling the options to configure the plugin will also go away if you exit out and go back in.
The timer bug is due to the way Windows handles .dll's. Since Java doesn't have a way of detecting how long a user is idle, I had to write some native Win32 code to do so. It works as long as you don't reload the plugin... which happens every time you configure ConsultComm. So as long as you don't make any configuration changes, the plugin should work.
I'll close this out once we verify the release candidate works for you. Thanks!
The next version will have these fixes and should be posted by tomorrow (Tuesday) night.
This issue has been posted to the Bugs tracker at http://sourceforge.net/projects/consultcomm/
Lemme know if the 3.1rc1 release that I posted yesterday doesn't take care of these problems for you.