Prime Community Forum

But yes go ahead and create an issue here: https://github.com/primefaces-extension ... com/issues

Reproducable with sample. He try only with content clear. Why didn't you try my homework sample? I made it for you for nothing? I don't understund you.
If you say that "we don't have money" I say that "why do you play with free and open source project?" You didn't say that, but I feel this. I made this project for represent your dyna form force and not a showcase but useable project. And you say "use space instead a comma" ? Sorry, it is ridiculous!

Sorry, I made this project since about 3 years, and it was not so easy. I'm tired now. Please help in my work.

Despite the fact I didn't understand your statement I would ask you to be more "diplomatic" in your posts. You have to understand that we use our free time and our good will when it comes to work on PF or PFE (and we also get tired )

How do you want people try your sample if you don't write a procedure to run it? (That on the other hand is ridiculous ) Since I have no clue how to do it, I used primefaces-test (https://github.com/primefaces/primefaces-test) and it works like a charm. BTW, you're using Servlet 3.1 with JSF API 2.2 and JSF Impl 2.1.3 and JEE 7, your dependencies are completely messed up... Fix that for the good of your project

I managed to reproduce your problem based on your sample. I'll try to find the problem ASAP, but be aware it can take some time. I understand how frustrating it is not getting a reply, I've been there (typically regarding a DynaForm problem and many other) but instead of waiting of answer I tried to find the solution by myself...

Yes, I know I'm not perfect. But I try growing.
Thanks for your patience. Several times I report and solve errors in PF but I not compiled PFE from source until now.

Disable attribute is not saved by the "Restorable saving state" mechanism set up in DynaForm. I have to figure something out about that... But you can workaround problem doing these 2 simple steps:

1. Removing "update" attribute" set on Disable button
2. Instead, use partial update in your visitor, right after you disable the component (e.g PrimeFaces.current().ajax().update(input.getClientId());)

Let me know if it works for you

It works for me, but it's not perfect workaround because new component addition must update the form.
Please see youtube here.
Maybe I can solve it with another Visitor that must run after each update but it's horrible extra effort.
I'll check and compile from source myself. Where should I search for this in source?

I fixed the issue on my side, I'll try to push that ASAP. If you plan to modify more properties like disabled programmatically, let me know

Fixed. I don't know when the next version will be released. You can test it by building from source

Thank you! The encodeStatic method is your modification for style encoding? So, can I use readonly, too?