TFNCMemo and FNCDataBinder

I am trying to bind the lines.text of a TFNCMemo via a TFNCDataBinder to a TdataSet field.
But this does not work. Neither binding to lines nor binding to lines.text. No error, but nothing is diaplayed.

What am I missing?

tx Bernd

Hi,

Lines have a Text property, but the Text property is not published, meaning we cannot access this property. There is currently no support for filling a TStringList. I've worked on the code, the next version of TMS FNC Core will have support for directly using the Lines property.

Thanks for the feedback.

Great to hear! Tx!

While the binding now works (tx!), there is something weird going on.
When there is a fncmemo on the form, wrinting to the binder messes up with the events.

See the enclosed demo. The first FNCEdit has an OnExit event, that writes to the binder.

Change the value of the FNCEdit1 and click Next. The name is changed (because of the write in the OnExit), but the OnClick of Next is not executed.

If you click to the next edit instead of the button and you move the mose, the content is selected without reason.

If you remove the memo, everyrthing works as expected.
projDataBinding.zip (6.8 KB)

Hi,

The TTMSFNCMemo is browser based and executes JavaScript. Because of the asynchronous nature of the browser, we need to await this and block the main thread. When this happens, we call Application.ProcessMessages to ensure the main thread can continue to distribute messages and handle events. In FMX however, it seems this corrupts the message queue. For now, we cannot provide a fix for the TMS FNC Memo, we'll investigate if there is a workaround.

I see.
I wonder, if there are plans for a simple FNC multi line component?

There are currently no plans. TMemo is simple multi-line editor and effective. Could you elaborate on which features on top of TMemo you might need?

Well, undo/redo, styling, persistence - whatever FNC components have in common.

Undo/Redo, Persistence is not tied to FNC specifically, it can be setup manually for any kind of object / control with published properties. Styling is indeed something specific for FNC, but what I meant was, if you are using TMemo, which features on TMemo specifically are you missing. I've tested the above setup with TMemo which works (as a temporary workaround)

No, nothing special, just a plain multiline Tmemo. Tmemo would be ok, of course, but why mix component families? This leads to a mess, when styling, data binding, ... , is involved.

Ofcourse, an FNC component would be benificial, we'll look into it.