QML and Qt Quick

solved :-) no one saw it ;-) public: QQmlListProperty<TestItem> lstTestItems() const; this can't be const. Thats it.

That example sometimes uses parent properties directly and sometimes with protection. What's the rule we should apply regarding whether to use null protection or not?

How do I edit the original post? I dont see that option listed anywhere on the page, just an option to reply.

@shwt.saxena Please format your code before pasting and use ``` (3 backticks) for posting code blocks. The code that you posted doesn't show how details screen in invoked. Is it is a Component or a separate QML ? Please post those details.

@HappyCoder Apart from using inputMask you will also need to set a validator. RegExpValidator would be perfect choice for it. A common validator for hh:mm:ss I found was this /^(?:(?:([01]?\d|2[0-3]):)?([0-5]?\d):)?([0-5]?\d)$/ Usage is simple: validator: RegExpValidator { regExp: /^(?:(?:([01]?\d|2[0-3]):)?([0-5]?\d):)?([0-5]?\d)$/ } You can also find another validators.

@beh_zad Thanks for sharing.

@Bremenpl It could be a bug. Please report it Qt BugTracker.

@joanaguimas Congratulations :) Happy Coding..

@p3c0 Thank you very much :)

Hi, Sounds like you should implement your own validator and check against a given list of words

@PhTe Well that too because you have visible set to true for Dialog. You're Welcome. Happy Coding..

@Juaruipav Yes it is activated. Did you try by deactivating it ? May be it is a bug on Windows 8.1. Better you should report it on Qt Bug Tracker.

@Buttink The attached properties are not always directly accessible by the children. It is documented here. It states: A common error is to assume that attached properties and signal handlers are directly accessible from the children of the object to which these attributes have been attached. This is not the case. The instance of the attaching type is only attached to specific objects, not to the object and all of its children. Check out the example provided there.

@pDogg As I said earlier it wont work. From the doc for containsMouse: Warning: This property is not updated if the area moves under the mouse: containsMouse will not change. In addition, if hoverEnabled is false, containsMouse will only be valid when the mouse is pressed while the mouse cursor is inside the MouseArea. I think you will need to calculate it manually.

I found a simple solution for my problem. I just declare a property Q_PROPERTY(QJSValue onMouseUp READ onMouseUp WRITE setOnMouseUp) that I can call from C++ side as QJSValue::call(). It allows me to write more clean code and ensure to have a single signal handler for this event (it's also important for me)

@svyatoslav911512 You can read more about property binding here. Happy coding..

It's hard to guess without more context, but if you're using Creator, try the "Run qmake" build option before building.

@Cyril You're Welcome :) However it gets a bit confused having anchors, width height, Layout. all for item placing I would suggest you go through following for more info : http://doc.qt.io/qt-5/qtquick-positioning-topic.html http://doc.qt.io/qt-5/qtquick-usecase-layouts.html