Feel like I am missing something, but how do you actually persist any changes back to the database? I can edit anything I want, but the changes never get back to the databases.
I'm not sure. Honestly, I've used DevExpress for years, but have yet to use this control. Maybe because I'm of the opinion data-binding to the form controls or even the project itself is the devil. I like my data to be flexible enough I can change databases and even database types at will without having to change any programming apart from the ADO.NET connector used. I just (re)watched the video to see if I was missing something. I was wondering if there was more to this control that I missed.
Hello! You will have some documentation to make changes in Layout Control at runtime and Save this Layout in an Xml or a database, so when you run the program again you do not have to make changes to the Layout control again.
i'm using access mdb i have created ole object for photo.. but when i paste or capture my photo, the picture edit say error near edit picture what i do?
love layout but its a pain in the %$$#% to bind code to it, to make it more "dynamic" and load in runtime in a winform..... its tricky with the spaces, many times one wrong placement of a control there is no undo just delete everything and design it from scratch...... and the performance while opening forms can become really bad while we wait for the xml to be loaded and applied from even a local database.....but i like it because its promising and offers flexible designs that project managers love to sell. :)
That's the control I'm looking and searching for days. Thanks to this video I can step forward.
Feel like I am missing something, but how do you actually persist any changes back to the database? I can edit anything I want, but the changes never get back to the databases.
saving more time to design controls thanks dev
How to save , delete or update??
I'm not sure. Honestly, I've used DevExpress for years, but have yet to use this control. Maybe because I'm of the opinion data-binding to the form controls or even the project itself is the devil. I like my data to be flexible enough I can change databases and even database types at will without having to change any programming apart from the ADO.NET connector used. I just (re)watched the video to see if I was missing something. I was wondering if there was more to this control that I missed.
Is there a way to show at runtime the databinding wizard?
Hello! You will have some documentation to make changes in Layout Control at runtime and Save this Layout in an Xml or a database, so when you run the program again you do not have to make changes to the Layout control again.
i'm using access mdb
i have created ole object for photo..
but when i paste or capture my photo, the picture edit say error near edit picture
what i do?
love layout but its a pain in the %$$#% to bind code to it, to make it more "dynamic" and load in runtime in a winform..... its tricky with the spaces, many times one wrong placement of a control there is no undo just delete everything and design it from scratch...... and the performance while opening forms can become really bad while we wait for the xml to be loaded and applied from even a local database.....but i like it because its promising and offers flexible designs that project managers love to sell. :)
What do you love that is not pain in the @55!@#!?
muy complejo
Dios Express! jaja