Inline Edit of Yes/No Field - Check for edit?

BLOMASKY

I get a Yes/No Combo box when editing a Yes/No field which has Icon rules, (so it shows a checkbox when true), It would be nice if the end-user could just click the field with the mouse to change (toggle) the value. Is this possible? Otherwise, this is not an intuative UI.

Thanks
Bruce

intra

Hi Bruce,

I'm keen to know if this is possible too.

I would like to use a 'switch' inline on a query (inline edit) for an electronic version of a 'in/out whiteboard'.

pureist

Checkbox attributes displayed as yes/no dropdowns in queries can instead be displayed as switches using a Custom Query, with a small amount of work.
But if you want to still be able to inline edit other fields, then it will require a bit more work again.

hpl123

BLOMASKY wrote
I get a Yes/No Combo box when editing a Yes/No field which has Icon rules, (so it shows a checkbox when true), It would be nice if the end-user could just click the field with the mouse to change (toggle) the value. Is this possible? Otherwise, this is not an intuative UI.

Thanks
Bruce

Bruce, take a look at this post:
https://forum.awareim.com/d/7644/1&hilit=custom+icon+operation#p31824

BLOMASKY

I see what you did Henrick, and I wish that would solve my problem, however, I have many cases where I have a editable grid and want the user to be able to just tick a check box field. Sort of like every other program works. This is not intuitive for the end user. They see a column with some checkboxes in it, then they want to toggle one, and instead of just clicking, they click, see a combo box, (which is wider than the check column!) and have to then click the yes or no.

Humm, Aware Support, Wonder how much it would cost to have this fixed????

Bruce

pureist

If you don't want to use a Custom Query, then what Henrick did will resolve your issue in a Standard Query scenario.
The user will be able to just tick a checkbox field.
However, instead of using an image for the checkbox (which is switched according to the checked state of the Checkbox Attribute itself) and updated via the Query being Refreshed, instead using:
<input type="checkbox" onchange=AwareApp.startProc..
in the Attribute (which contains HTML) displayed in the Query in place of the Checkbox Attribute, would possibly yield a more seamless UI transition from unchecked-checked-unchecked, as the Query will not need to Refresh.
However, users are still going to see the annoying 'veil' for a moment when the Process is run (following the checkbox being changed) to Update the Checkbox Attribute and the Attribute containing HTML which is displayed in its place in a Query.

BLOMASKY wrote
I see what you did Henrick, and I wish that would solve my problem, however, I have many cases where I have a editable grid and want the user to be able to just tick a check box field.
Bruce

hpl123

pureist wrote
If you don't want to use a Custom Query, then what Henrick did will resolve your issue in a Standard Query scenario.
The user will be able to just tick a checkbox field.
However, instead of using an image for the checkbox (which is switched according to the checked state of the Checkbox Attribute itself) and updated via the Query being Refreshed, instead using:
<input type="checkbox" onchange=AwareApp.startProc..
in the Attribute (which contains HTML) displayed in the Query in place of the Checkbox Attribute, would possibly yield a more seamless UI transition from unchecked-checked-unchecked, as the Query will not need to Refresh.
However, users are still going to see the annoying 'veil' for a moment when the Process is run (following the checkbox being changed) to Update the Checkbox Attribute and the Attribute containing HTML which is displayed in its place in a Query.

BLOMASKY wrote
I see what you did Henrick, and I wish that would solve my problem, however, I have many cases where I have a editable grid and want the user to be able to just tick a check box field.
Bruce

Yes, this would solve it and nice addition with the input type thingy, I hadn´t thought of that.

Sidenote:
Quote "However, users are still going to see the annoying 'veil' for a moment when the Process is run" yes, this is very annoying and something I have thought many times about and I would love a way to disable this feature for certain processes when needed and this is a very good example of when/why this would be useful.

hpl123

pureist wrote
If you don't want to use a Custom Query, then what Henrick did will resolve your issue in a Standard Query scenario.
The user will be able to just tick a checkbox field.
However, instead of using an image for the checkbox (which is switched according to the checked state of the Checkbox Attribute itself) and updated via the Query being Refreshed, instead using:
<input type="checkbox" onchange=AwareApp.startProc..
in the Attribute (which contains HTML) displayed in the Query in place of the Checkbox Attribute, would possibly yield a more seamless UI transition from unchecked-checked-unchecked, as the Query will not need to Refresh.
However, users are still going to see the annoying 'veil' for a moment when the Process is run (following the checkbox being changed) to Update the Checkbox Attribute and the Attribute containing HTML which is displayed in its place in a Query.

BLOMASKY wrote
I see what you did Henrick, and I wish that would solve my problem, however, I have many cases where I have a editable grid and want the user to be able to just tick a check box field.
Bruce

Doesn´t seem to work or did you get it to work with input type checkbox pureist?

hpl123

hpl123 wrote
pureist wrote
If you don't want to use a Custom Query, then what Henrick did will resolve your issue in a Standard Query scenario.
The user will be able to just tick a checkbox field.
However, instead of using an image for the checkbox (which is switched according to the checked state of the Checkbox Attribute itself) and updated via the Query being Refreshed, instead using:
<input type="checkbox" onchange=AwareApp.startProc..
in the Attribute (which contains HTML) displayed in the Query in place of the Checkbox Attribute, would possibly yield a more seamless UI transition from unchecked-checked-unchecked, as the Query will not need to Refresh.
However, users are still going to see the annoying 'veil' for a moment when the Process is run (following the checkbox being changed) to Update the Checkbox Attribute and the Attribute containing HTML which is displayed in its place in a Query.

BLOMASKY wrote
I see what you did Henrick, and I wish that would solve my problem, however, I have many cases where I have a editable grid and want the user to be able to just tick a check box field.
Bruce

Doesn´t seem to work or did you get it to work with input type checkbox pureist?

There is a bug here and is the reason it doens´t work. I will prepare sample BSV for support.

pureist

I discovered by accident that Attribute Values beginning with < and ending with > were treated as HTML, when a Grid Cell was empty despite the Attribute having a Value (enclosed in < >).
I still think it is an 'irregular behavior' which should not occur (or should be an option).
But obviously it can have a use, and you can use a Rule to prevent the user from entering such Attribute Values.

It was working fine with onChange and onClick, at the beginning of the year, in a Custom Query.
I've just assumed a checkbox will also work in HTML Attribute Values because every other Control displayed via an HTML Attribute Value did.

hpl123 wrote
Doesn´t seem to work or did you get it to work with input type checkbox pureist?