application

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-5754: Implementation

- Code clean up

    • -2
    • +1
    /sources/gui/qml/components/GridSelection.qml
    • -0
    • +66
    /sources/gui/qml/components/StepBullet.qml
    • -0
    • +86
    /sources/gui/qml/components/StepIndicator.qml
    • -0
    • +5
    /sources/gui/qml/globals/Variables.qml
    • -10
    • +10
    /sources/gui/qml/pages/treatment/TreatmentStack.qml
Thanks, these links are helpful

Thanks, these links are helpful

Thanks, only a Numeric keyboard in this case. Please also take a look at the KDAB training about the QtQuick keyboard handling, in https://www.youtube.com/watch?v=ilCekEOpNYM @ 5:40 using the Keys ...

Thanks, only a Numeric keyboard in this case.
Please also take a look at the KDAB training about the QtQuick keyboard handling, in https://www.youtube.com/watch?v=ilCekEOpNYM @ 5:40 using the Keys API to be able to navigate on 'enter' pressed.
that might be helpful.
I think it should be "enterPressed", "returnPressed", or both.

Please also take a look at the UX desing in the link : https://app.zeplin.io/project/5db0c175acfeac55e3cb879e/screen/5dbc8461bab7462c152cb34e

Okay, sure no problem. Do you want the full qwerty keyboard then or numeric-only for this screen?

Okay, sure no problem. Do you want the full qwerty keyboard then or numeric-only for this screen?

Thanks for providing the screenshots to compare. I would vote for the default style which covers half the screen since it is more standard and would be the same all over the application instead of ...

Thanks for providing the screenshots to compare.
I would vote for the default style which covers half the screen since it is more standard and would be the same all over the application instead of having different keyboard combinations and locations in different situations and prefer to relocate screen components and labeling to fit in the screen.
It can be like :

                                  Vitals Entry
                                ------------------
   systolic [   ___    ]        diastolic [   ___    ]        BPM [   ___    ]

(or labels at top)


and hide the keyboard on last entry BPM, 'enter' touch.
Also, please on the user 'enter' touch go to the next entry.

You can't adjust the size of the keyboard, change what buttons are available, or adjust the opaque black background that's blocking half the screen without adjusting the styling. In here you will ...

You can't adjust the size of the keyboard, change what buttons are available, or adjust the opaque black background that's blocking half the screen without adjusting the styling.

In here you will find a couple of screenshots for comparison:

Default numeric styling:
X:\Users\PeterL\ForBehrouz\Vitals_Entry_Default_Numeric_Keyboard.png

Custom numeric styling:
X:\Users\PeterL\ForBehrouz\Vitals_Numeric_Keyboard.png

Full Qwerty Keyboard with default styling:
X:\Users\PeterL\ForBehrouz\Full_Qwerty_Keyboard.png

Very dangerous use of pointers please consider using none pointer variables. as an example why _lastSelectedDevice has been defined as a pointer? Please keep that in mind there is no guaranty that ...

Very dangerous use of pointers please consider using none pointer variables.
as an example why _lastSelectedDevice has been defined as a pointer?
Please keep that in mind there is no guaranty that your code will reach the pointer release, and exceptions can happen anytime.

Why a simple name, address value set has been converted to a Jason Document by that complicated dereferencing and casting of pointers and passed over all the stacks of signal/slots instead of a sim...

Why a simple name, address value set has been converted to a Jason Document by that complicated dereferencing and casting of pointers and passed over all the stacks of signal/slots instead of a simple struct?

why 9999 used for default value instead of zero?

why 9999 used for default value instead of zero?

please use #pragma once

please use #pragma once

please move all the private member variables to the default private section of the class.

please move all the private member variables to the default private section of the class.

please use (const &) for all the slots down here.

please use (const &) for all the slots down here.

please a complete argument (const TYPE &vArgument)

please a complete argument (const TYPE &vArgument)

same here for arguments name

same here for arguments name

please use the 'v' for the argument name beginning.

please use the 'v' for the argument name beginning.

please use nullptr instead of the NULL.

please use nullptr instead of the NULL.

Please look at the zeplin, 3.3 Name New Treatment Screen for the text entry UX design.

Please look at the zeplin, 3.3 Name New Treatment Screen for the text entry UX design.

Where the color has been picked from? If it is from UX design from zeplin, keep that in mind it wasn't a final design and has been put there to imply that the page requires a keyboard. what is the ...

Where the color has been picked from?
If it is from UX design from zeplin, keep that in mind it wasn't a final design and has been put there to imply that the page requires a keyboard.
what is the default color?

Where these values come from and please define them in the Variables file under the PRS section if applicable?

Where these values come from and please define them in the Variables file under the PRS section if applicable?

same here.

same here.

same here.

same here.

same here.

same here.

Please don't forget the translation for all the translatable strings.

Please don't forget the translation for all the translatable strings.

Please change the file name to TextEntry or TextEdit to make it more general (but not TextInput which conflicts with QtQuick). Field most of the time refers to a database field which is not the cas...

Please change the file name to TextEntry or TextEdit to make it more general (but not TextInput which conflicts with QtQuick).
Field most of the time refers to a database field which is not the case all the time for this component.

why QtQuick.Controls imported?

why QtQuick.Controls imported?

Please don't use ";" until it's absolutely necessary, especially in qml codes.

Please don't use ";" until it's absolutely necessary, especially in qml codes.

please use "Item" instead of "Rectangle" with color as transparent when possible.

please use "Item" instead of "Rectangle" with color as transparent when possible.

please use "Item" instead of "Rectangle" with color as transparent when possible.

please use "Item" instead of "Rectangle" with color as transparent when possible.

please whenever possible use the QtQuick versions instead of the QtQuick.controls. So in this case TextInput can be used instead of TextField. And then please remove the "import QtQuick.Controls 2.12"

please whenever possible use the QtQuick versions instead of the QtQuick.controls.
So in this case TextInput can be used instead of TextField.
And then please remove the "import QtQuick.Controls 2.12"

Why does it even need styling? Couldn't we use the keyboard default styling? Please provide two of the default and styled screenshot versions of the keyboard for comparison.

Why does it even need styling?
Couldn't we use the keyboard default styling?
Please provide two of the default and styled screenshot versions of the keyboard for comparison.