Qt-interest Archive, September 2007
Re: QDataWidgetMapper Questions
Message 1 in thread
Ok, I now have one more to add to the below list- if a boolean MySQL
field is mapped to a check box widget, the widget properly displays
the value of the field, but clicking it doesn't change the value. The
obvious work around for this, of course, is writing a slot for the
onStateChanged or toggled signals of the check boxes that updates the
underlying QSqlTableModel manually, but the mapper should make this
unnecessary. Anyone have a solution for any of these issues? I'd
REALLY like to get them resolved. Thanks.
-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
On Aug 31, 2007, at 12:48 PM, Israel Brewster wrote:
> I am developing an SQL application using Qt 4.3.1, primarily on the
> Mac although I plan to run it on windows as well eventually (if it
> works). At the moment I am running into three somewhat annoying
> quirks while using QDataWidgetMapper to map the SQL fields (using
> QSqlRelationalTableModel or QSqlTableModel) to various GUI elements.
>
> 1) With a SQL field mapped to a LineEdit widget, if the user types
> in the LineEdit and then hits enter while still in the field (which
> is programed to save the record and close the window), the value
> just typed in the LineEdit widget is not saved back to the database-
> they have to first tab out of the LineEdit before hitting enter to
> actually save the changes. Once tabbed out of the LineEdit,
> however, the save works properly as expected. The enter key is
> triggering the OnClicked signal of the default button directly, not
> the onEnterPressed signal of the LineEdit.
>
> 2) A textEdit widget with a SQL field mapped to it behaves oddly
> when the enter key is pressed. A new line is created at the point
> of the cursor, as it should be, but the cursor then jumps to the
> beginning of the TextEdit widget. If I remove the line in the code
> that maps the SQL field to the TextEdit widget and make no other
> changes, the widget behaves properly.
>
> 3) Combo boxes mapped to a field in an SqlRelationalTableModel do
> not display the current value. Using the setModel and
> setModelColumn functions of the combo boxes I can get them to
> display the list of available values properly, and by using the
> QDataWidgetMapper, which is set to use the QSqlRelationalDelegate,
> setting the combo boxes properly sets the SQL record (with the
> exception of the situation mentioned in problem 1), but they always
> initially come up blank. Other form elements, such as LineEdits,
> show the value properly.
>
> I have come up with various workarounds for numbers 1 and 3, such
> as using the setData functionality of the QSqlTableModel to
> manually set the field equal to the value of the line edit before
> submitting, but they all seem like kludgy workarounds that I
> shouldn't need, and I am at a total loss for number 2. Can anyone
> help me find the proper solutions to these issues? Thanks.
>
> -----------------------------------------------
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> -----------------------------------------------
>
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 2 in thread
Partial solution - for the checkbox and lineEdit not updating the SQL
table, I discovered that calling the submit function of the MAPPER
rather than the QSqlTableModel fixed these issues (apparently, at
least) I still need a solution for the textEdit and combo box issues,
however, so anyone who can help it would be appreciated. Thanks!
-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
On Sep 4, 2007, at 8:04 AM, Israel Brewster wrote:
> Ok, I now have one more to add to the below list- if a boolean
> MySQL field is mapped to a check box widget, the widget properly
> displays the value of the field, but clicking it doesn't change the
> value. The obvious work around for this, of course, is writing a
> slot for the onStateChanged or toggled signals of the check boxes
> that updates the underlying QSqlTableModel manually, but the mapper
> should make this unnecessary. Anyone have a solution for any of
> these issues? I'd REALLY like to get them resolved. Thanks.
>
> -----------------------------------------------
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> -----------------------------------------------
>
>
> On Aug 31, 2007, at 12:48 PM, Israel Brewster wrote:
>
>> I am developing an SQL application using Qt 4.3.1, primarily on
>> the Mac although I plan to run it on windows as well eventually
>> (if it works). At the moment I am running into three somewhat
>> annoying quirks while using QDataWidgetMapper to map the SQL
>> fields (using QSqlRelationalTableModel or QSqlTableModel) to
>> various GUI elements.
>>
>> 1) With a SQL field mapped to a LineEdit widget, if the user types
>> in the LineEdit and then hits enter while still in the field
>> (which is programed to save the record and close the window), the
>> value just typed in the LineEdit widget is not saved back to the
>> database-they have to first tab out of the LineEdit before hitting
>> enter to actually save the changes. Once tabbed out of the
>> LineEdit, however, the save works properly as expected. The enter
>> key is triggering the OnClicked signal of the default button
>> directly, not the onEnterPressed signal of the LineEdit.
>>
>> 2) A textEdit widget with a SQL field mapped to it behaves oddly
>> when the enter key is pressed. A new line is created at the point
>> of the cursor, as it should be, but the cursor then jumps to the
>> beginning of the TextEdit widget. If I remove the line in the code
>> that maps the SQL field to the TextEdit widget and make no other
>> changes, the widget behaves properly.
>>
>> 3) Combo boxes mapped to a field in an SqlRelationalTableModel do
>> not display the current value. Using the setModel and
>> setModelColumn functions of the combo boxes I can get them to
>> display the list of available values properly, and by using the
>> QDataWidgetMapper, which is set to use the QSqlRelationalDelegate,
>> setting the combo boxes properly sets the SQL record (with the
>> exception of the situation mentioned in problem 1), but they
>> always initially come up blank. Other form elements, such as
>> LineEdits, show the value properly.
>>
>> I have come up with various workarounds for numbers 1 and 3, such
>> as using the setData functionality of the QSqlTableModel to
>> manually set the field equal to the value of the line edit before
>> submitting, but they all seem like kludgy workarounds that I
>> shouldn't need, and I am at a total loss for number 2. Can anyone
>> help me find the proper solutions to these issues? Thanks.
>>
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>>
>>
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>> with "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 3 in thread
Have a look at:
http://doc.trolltech.com/4.3/qdatawidgetmapper.html#submitPolicy-prop
If you use QDataWidgetMapper::AutoSubmit every change will be submitted
to the model.
Israel Brewster schrieb:
> Partial solution - for the checkbox and lineEdit not updating the SQL
> table, I discovered that calling the submit function of the MAPPER
> rather than the QSqlTableModel fixed these issues (apparently, at least)
> I still need a solution for the textEdit and combo box issues, however,
> so anyone who can help it would be appreciated. Thanks!
>
> -----------------------------------------------
> Israel Brewster
> Computer Support Technician
> Frontier Flying Service Inc.
> 5245 Airport Industrial Rd
> Fairbanks, AK 99709
> (907) 450-7250 x293
> -----------------------------------------------
>
>
> On Sep 4, 2007, at 8:04 AM, Israel Brewster wrote:
>
>> Ok, I now have one more to add to the below list- if a boolean MySQL
>> field is mapped to a check box widget, the widget properly displays
>> the value of the field, but clicking it doesn't change the value. The
>> obvious work around for this, of course, is writing a slot for the
>> onStateChanged or toggled signals of the check boxes that updates the
>> underlying QSqlTableModel manually, but the mapper should make this
>> unnecessary. Anyone have a solution for any of these issues? I'd
>> REALLY like to get them resolved. Thanks.
>>
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>>
>>
>> On Aug 31, 2007, at 12:48 PM, Israel Brewster wrote:
>>
>>> I am developing an SQL application using Qt 4.3.1, primarily on the
>>> Mac although I plan to run it on windows as well eventually (if it
>>> works). At the moment I am running into three somewhat annoying
>>> quirks while using QDataWidgetMapper to map the SQL fields (using
>>> QSqlRelationalTableModel or QSqlTableModel) to various GUI elements.
>>>
>>> 1) With a SQL field mapped to a LineEdit widget, if the user types in
>>> the LineEdit and then hits enter while still in the field (which is
>>> programed to save the record and close the window), the value just
>>> typed in the LineEdit widget is not saved back to the database-they
>>> have to first tab out of the LineEdit before hitting enter to
>>> actually save the changes. Once tabbed out of the LineEdit, however,
>>> the save works properly as expected. The enter key is triggering the
>>> OnClicked signal of the default button directly, not the
>>> onEnterPressed signal of the LineEdit.
>>>
>>> 2) A textEdit widget with a SQL field mapped to it behaves oddly when
>>> the enter key is pressed. A new line is created at the point of the
>>> cursor, as it should be, but the cursor then jumps to the beginning
>>> of the TextEdit widget. If I remove the line in the code that maps
>>> the SQL field to the TextEdit widget and make no other changes, the
>>> widget behaves properly.
>>>
>>> 3) Combo boxes mapped to a field in an SqlRelationalTableModel do not
>>> display the current value. Using the setModel and setModelColumn
>>> functions of the combo boxes I can get them to display the list of
>>> available values properly, and by using the QDataWidgetMapper, which
>>> is set to use the QSqlRelationalDelegate, setting the combo boxes
>>> properly sets the SQL record (with the exception of the situation
>>> mentioned in problem 1), but they always initially come up blank.
>>> Other form elements, such as LineEdits, show the value properly.
>>>
>>> I have come up with various workarounds for numbers 1 and 3, such as
>>> using the setData functionality of the QSqlTableModel to manually set
>>> the field equal to the value of the line edit before submitting, but
>>> they all seem like kludgy workarounds that I shouldn't need, and I am
>>> at a total loss for number 2. Can anyone help me find the proper
>>> solutions to these issues? Thanks.
>>>
>>> -----------------------------------------------
>>> Israel Brewster
>>> Computer Support Technician
>>> Frontier Flying Service Inc.
>>> 5245 Airport Industrial Rd
>>> Fairbanks, AK 99709
>>> (907) 450-7250 x293
>>> -----------------------------------------------
>>>
>>>
>>> --
>>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>>> with "unsubscribe" in the subject or the body.
>>> List archive and information: http://lists.trolltech.com/qt-interest/
>>
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
>> "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 4 in thread
BTW: QDataWidgetMapper is buggy... and can cause serious trouble:
http://trolltech.com/developer/task-tracker/index_html?method=entry&id=172427
We have an own implementation. If you are interested, contact me via email.
Greetings
Niklas
Niklas Hofmann schrieb:
> Have a look at:
> http://doc.trolltech.com/4.3/qdatawidgetmapper.html#submitPolicy-prop
>
> If you use QDataWidgetMapper::AutoSubmit every change will be submitted
> to the model.
>
>
> Israel Brewster schrieb:
>> Partial solution - for the checkbox and lineEdit not updating the SQL
>> table, I discovered that calling the submit function of the MAPPER
>> rather than the QSqlTableModel fixed these issues (apparently, at
>> least) I still need a solution for the textEdit and combo box issues,
>> however, so anyone who can help it would be appreciated. Thanks!
>>
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>>
>>
>> On Sep 4, 2007, at 8:04 AM, Israel Brewster wrote:
>>
>>> Ok, I now have one more to add to the below list- if a boolean MySQL
>>> field is mapped to a check box widget, the widget properly displays
>>> the value of the field, but clicking it doesn't change the value. The
>>> obvious work around for this, of course, is writing a slot for the
>>> onStateChanged or toggled signals of the check boxes that updates the
>>> underlying QSqlTableModel manually, but the mapper should make this
>>> unnecessary. Anyone have a solution for any of these issues? I'd
>>> REALLY like to get them resolved. Thanks.
>>>
>>> -----------------------------------------------
>>> Israel Brewster
>>> Computer Support Technician
>>> Frontier Flying Service Inc.
>>> 5245 Airport Industrial Rd
>>> Fairbanks, AK 99709
>>> (907) 450-7250 x293
>>> -----------------------------------------------
>>>
>>>
>>> On Aug 31, 2007, at 12:48 PM, Israel Brewster wrote:
>>>
>>>> I am developing an SQL application using Qt 4.3.1, primarily on the
>>>> Mac although I plan to run it on windows as well eventually (if it
>>>> works). At the moment I am running into three somewhat annoying
>>>> quirks while using QDataWidgetMapper to map the SQL fields (using
>>>> QSqlRelationalTableModel or QSqlTableModel) to various GUI elements.
>>>>
>>>> 1) With a SQL field mapped to a LineEdit widget, if the user types
>>>> in the LineEdit and then hits enter while still in the field (which
>>>> is programed to save the record and close the window), the value
>>>> just typed in the LineEdit widget is not saved back to the
>>>> database-they have to first tab out of the LineEdit before hitting
>>>> enter to actually save the changes. Once tabbed out of the LineEdit,
>>>> however, the save works properly as expected. The enter key is
>>>> triggering the OnClicked signal of the default button directly, not
>>>> the onEnterPressed signal of the LineEdit.
>>>>
>>>> 2) A textEdit widget with a SQL field mapped to it behaves oddly
>>>> when the enter key is pressed. A new line is created at the point of
>>>> the cursor, as it should be, but the cursor then jumps to the
>>>> beginning of the TextEdit widget. If I remove the line in the code
>>>> that maps the SQL field to the TextEdit widget and make no other
>>>> changes, the widget behaves properly.
>>>>
>>>> 3) Combo boxes mapped to a field in an SqlRelationalTableModel do
>>>> not display the current value. Using the setModel and setModelColumn
>>>> functions of the combo boxes I can get them to display the list of
>>>> available values properly, and by using the QDataWidgetMapper, which
>>>> is set to use the QSqlRelationalDelegate, setting the combo boxes
>>>> properly sets the SQL record (with the exception of the situation
>>>> mentioned in problem 1), but they always initially come up blank.
>>>> Other form elements, such as LineEdits, show the value properly.
>>>>
>>>> I have come up with various workarounds for numbers 1 and 3, such as
>>>> using the setData functionality of the QSqlTableModel to manually
>>>> set the field equal to the value of the line edit before submitting,
>>>> but they all seem like kludgy workarounds that I shouldn't need, and
>>>> I am at a total loss for number 2. Can anyone help me find the
>>>> proper solutions to these issues? Thanks.
>>>>
>>>> -----------------------------------------------
>>>> Israel Brewster
>>>> Computer Support Technician
>>>> Frontier Flying Service Inc.
>>>> 5245 Airport Industrial Rd
>>>> Fairbanks, AK 99709
>>>> (907) 450-7250 x293
>>>> -----------------------------------------------
>>>>
>>>>
>>>> --
>>>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>>>> with "unsubscribe" in the subject or the body.
>>>> List archive and information: http://lists.trolltech.com/qt-interest/
>>>
>>> --
>>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>>> with "unsubscribe" in the subject or the body.
>>> List archive and information: http://lists.trolltech.com/qt-interest/
>>
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
>> "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 5 in thread
> Interesting situation. With my current development, I wouldn't expect to run into that particular bug (the areas where I am using a mapper and the areas where I am using a table view are completely separate, as far as the data models are concerned), but I would be interested in seeing a fix, in the case that I want to write something this way. Thanks!
>
Problem: this is a situation, where you see some consequences. The bug
is also in the normal use case existent and causes a weird behaviour
sometimes.
--
[ signature omitted ]
Message 6 in thread
On Sep 4, 2007, at 9:17 AM, Niklas Hofmann wrote:
> Have a look at:
> http://doc.trolltech.com/4.3/qdatawidgetmapper.html#submitPolicy-prop
>
> If you use QDataWidgetMapper::AutoSubmit every change will be
> submitted to the model.
Thanks for the link. However, your statement isn't quite correct: if
you use QDataWidgetMapper::AutoSubmit every change will be submitted
to the model "WHENEVER A WIDGET LOOSES FOCUS". (quoting from above
link, emphasis mine). Unfortunately, this is a very major caveat- if
the user makes a change in a lineEdit, and then hits enter while
still in the lineEdit, the widget never looses focus (or at least not
until after the model changes have been submitted to the MySQL
database), and so the changes AREN'T submitted to the model, and the
database is not updated. Similarly, with a check box widget, when the
user clicks it, it never gets the focus in the first place, so it
never looses the focus, so the change is never submitted to the
model. Apparently you have to manually call the submit() slot on the
mapper, and not the model, to get these types of changes submitted.
-----------------------------------------------
Israel Brewster
Computer Support Technician
Frontier Flying Service Inc.
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x293
-----------------------------------------------
>
>
> Israel Brewster schrieb:
>> Partial solution - for the checkbox and lineEdit not updating the
>> SQL table, I discovered that calling the submit function of the
>> MAPPER rather than the QSqlTableModel fixed these issues
>> (apparently, at least) I still need a solution for the textEdit
>> and combo box issues, however, so anyone who can help it would be
>> appreciated. Thanks!
>> -----------------------------------------------
>> Israel Brewster
>> Computer Support Technician
>> Frontier Flying Service Inc.
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7250 x293
>> -----------------------------------------------
>> On Sep 4, 2007, at 8:04 AM, Israel Brewster wrote:
>>> Ok, I now have one more to add to the below list- if a boolean
>>> MySQL field is mapped to a check box widget, the widget properly
>>> displays the value of the field, but clicking it doesn't change
>>> the value. The obvious work around for this, of course, is
>>> writing a slot for the onStateChanged or toggled signals of the
>>> check boxes that updates the underlying QSqlTableModel manually,
>>> but the mapper should make this unnecessary. Anyone have a
>>> solution for any of these issues? I'd REALLY like to get them
>>> resolved. Thanks.
>>>
>>> -----------------------------------------------
>>> Israel Brewster
>>> Computer Support Technician
>>> Frontier Flying Service Inc.
>>> 5245 Airport Industrial Rd
>>> Fairbanks, AK 99709
>>> (907) 450-7250 x293
>>> -----------------------------------------------
>>>
>>>
>>> On Aug 31, 2007, at 12:48 PM, Israel Brewster wrote:
>>>
>>>> I am developing an SQL application using Qt 4.3.1, primarily on
>>>> the Mac although I plan to run it on windows as well eventually
>>>> (if it works). At the moment I am running into three somewhat
>>>> annoying quirks while using QDataWidgetMapper to map the SQL
>>>> fields (using QSqlRelationalTableModel or QSqlTableModel) to
>>>> various GUI elements.
>>>>
>>>> 1) With a SQL field mapped to a LineEdit widget, if the user
>>>> types in the LineEdit and then hits enter while still in the
>>>> field (which is programed to save the record and close the
>>>> window), the value just typed in the LineEdit widget is not
>>>> saved back to the database-they have to first tab out of the
>>>> LineEdit before hitting enter to actually save the changes. Once
>>>> tabbed out of the LineEdit, however, the save works properly as
>>>> expected. The enter key is triggering the OnClicked signal of
>>>> the default button directly, not the onEnterPressed signal of
>>>> the LineEdit.
>>>>
>>>> 2) A textEdit widget with a SQL field mapped to it behaves oddly
>>>> when the enter key is pressed. A new line is created at the
>>>> point of the cursor, as it should be, but the cursor then jumps
>>>> to the beginning of the TextEdit widget. If I remove the line in
>>>> the code that maps the SQL field to the TextEdit widget and make
>>>> no other changes, the widget behaves properly.
>>>>
>>>> 3) Combo boxes mapped to a field in an SqlRelationalTableModel
>>>> do not display the current value. Using the setModel and
>>>> setModelColumn functions of the combo boxes I can get them to
>>>> display the list of available values properly, and by using the
>>>> QDataWidgetMapper, which is set to use the
>>>> QSqlRelationalDelegate, setting the combo boxes properly sets
>>>> the SQL record (with the exception of the situation mentioned in
>>>> problem 1), but they always initially come up blank. Other form
>>>> elements, such as LineEdits, show the value properly.
>>>>
>>>> I have come up with various workarounds for numbers 1 and 3,
>>>> such as using the setData functionality of the QSqlTableModel to
>>>> manually set the field equal to the value of the line edit
>>>> before submitting, but they all seem like kludgy workarounds
>>>> that I shouldn't need, and I am at a total loss for number 2.
>>>> Can anyone help me find the proper solutions to these issues?
>>>> Thanks.
>>>>
>>>> -----------------------------------------------
>>>> Israel Brewster
>>>> Computer Support Technician
>>>> Frontier Flying Service Inc.
>>>> 5245 Airport Industrial Rd
>>>> Fairbanks, AK 99709
>>>> (907) 450-7250 x293
>>>> -----------------------------------------------
>>>>
>>>>
>>>> --
>>>> To unsubscribe - send a mail to qt-interest-
>>>> request@xxxxxxxxxxxxx with "unsubscribe" in the subject or the
>>>> body.
>>>> List archive and information: http://lists.trolltech.com/qt-
>>>> interest/
>>>
>>> --
>>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>>> with "unsubscribe" in the subject or the body.
>>> List archive and information: http://lists.trolltech.com/qt-
>>> interest/
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
>> with "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx
> with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 7 in thread
Hi!
>> Have a look at:
>> http://doc.trolltech.com/4.3/qdatawidgetmapper.html#submitPolicy-prop
>>
>> If you use QDataWidgetMapper::AutoSubmit every change will be
>> submitted to the model.
>
> Thanks for the link. However, your statement isn't quite correct: if you
> use QDataWidgetMapper::AutoSubmit every change will be submitted to the
> model "WHENEVER A WIDGET LOOSES FOCUS". (quoting from above link,
> emphasis mine).
This is true - I use it only this way.. therefore.. ;)..
If you want a different behaviour, you should implement your own
DataWidgetMapper. It is a task of 2-3 hours.. not more.
Offer: You can use our implementation as basis.
Greetings
Niklas
--
[ signature omitted ]
