craftleft.gif (3002 bytes)QuickTable
Home | API | Tutorial | Download | Support | Contact topblack.gif (108 bytes)


QuickTable User Cp  |  Register  |  Members  |  Search  |  Help
    |- QuickTable Discussion Forums > Applet Issues Post New Topic   Post A Reply
applet problems printer friendly version
next newest post | next oldest post
Author Messages
armin.Weiser{@}freenet.de
Unregistered
Edit or delete this message Reply w/Quote
Posted Wednesday, December 31, 1969 @ 23:59:59  

My problem is that Quicktable doesn't use my own ErrorListener-, CellListener- and the ChangeListenerclasses when running in an applet. It is working fine in applications.
Do you have an idea ?
Another question is:
Quicktable updates data only when changing the row. Is it possible to make Quicktable able to update when the cellValue is changed ?
admin{@}quicktable.org
Unregistered
Edit or delete this message Reply w/Quote
Posted Wednesday, December 31, 1969 @ 23:59:59  

Please check your java console for any errors. When I tested ErrorListener, CellListener and DatabaseChangeListener, it worked fine in applets.

Regarding saving data to database, You are right, Quicktable updates the database when the row is changed. QuickTable doesn't update database once the cell value is changed. I am planning to add this feature to QuickTable, but can you give me a reason, why this option is really necessary? This option is not advisable because it increases the number of database calls. Also QuickTable provides a method save(), which can be called whenever you want to save the data.

Ben

armin.Weiser{@}freenet.de
Unregistered
Edit or delete this message Reply w/Quote
Posted Wednesday, December 31, 1969 @ 23:59:59  

Hi Ben,

thanks for your reply. I checked everything and I found the problem (it's not an applet problem, maybe its not a problem at all):
when I add the Listeners to Quicktable, they are in, but when I refresh stuff (clearAllSettings, giving columns new properties, refresh), I have to add them again, even if they should be the same (e.g. the errorlistener I don't want to exchange).

You are right, it is not advisable to increase database traffic, but in my case I need to be sure that all changed data immediately is in the database, I don't want to give any user the chance to make a mistake in this (imagine the user changes a cell, goes out for lunch, thinking anything is saved, while his computer freezes). Ok, it might be not that important. There is another feature I would prefer using. It has been posted as a wish before (message_number=171):
extension of the boundSQL-method:
"... I'd like to have a similar thing with the boundSQl where I could build a select with two values (value and description), the description would show and the value would be placed into the file. Just an idea.. "

Thank you for this most useful tool,
Armin.

admin{@}quicktable.org
Unregistered
Edit or delete this message Reply w/Quote
Posted Wednesday, December 31, 1969 @ 23:59:59  

clearAllsettings removes the listener because, users change the select sql and they forget to add new listeners based on the new selectsql. This results in strange behaviours. Removing the listeners in clearallsettings forces them to create new listeners based on current sql. If you are using the same sql & if you want to reuse the same listeners, you don't have to call clearAllSettings.

I will give an option to save immediately once the user updates a cell in the next version of Quicktable. Also I will add the feature for bound sql which you have requested in next version.

Ben

Post New Topic   Post A Reply Jump to:
Contact Us | QuickTable - A Java DBGrid | Privacy Policy All times are GMT -5 Hours.
Welcome to QuickTable Forums, Guest!  
Login
Username :
Password :
In order to fully utilize the abilities of this board, you are required to register as a member. Registration is free, and allows you to do lots of things including turning on or off certain features of this board. Register now!
Powered by CuteCast v2.0 BETA 2
Copyright © 2001-2003 ArtsCore Studios