-
Notifications
You must be signed in to change notification settings - Fork 24
No property, bindable property, or event found for 'StepColor' #20
Comments
Hi @deanilvincent, Just to confirm, you're referring to a gradient, like this Xaml markup from https://github.com/tbaggett/xfgloss/blob/master/XFGlossSample/Examples/Views/Xaml/BackgroundGradientPage.xaml, right?
If so, you should be able to specify a binding for the StepColor property, like this for example, where GradientColor1 is a Xamarin.Forms.Color property on your view model:
I reviewed the code for StepColor and it is set up for detecting property changed notifications, so the above should work. If this is how you have it set up and it isn't working, can you provide a copy of your view model and view sources files? Its okay to remove unrelated stuff from them if needed. |
Hello @tbaggett Thank you for your quick response :) Yeah, I'm following those syntax for xaml. I can provide my codes here: Here's my Xaml
Here's my ViewModel
I can't really able to run or build it since the error is pointing in my xaml that says,
Thank you in advance :) |
Okay great, thanks for the confirmation. Unfortunately I won't have a chance to look at this for a few weeks. I will let you know when a new version is released to address this. |
Oh I understand. It is fine. :) Just let me know when new release has been added. :D |
Thanks man. I wish you a great and safe day :) |
Hello @tbaggett How is it going? :) |
Hi @deanilvincent, I'm still trying to wrap up my current contract project. I am planning to work on XFGloss as soon as the current project is done. |
Hello @tbaggett Oh cool. Sure, take your time. Thank you for your quick response :) |
Hi @deanilvincent, fyi I finally got an update out that adds Netstandard 2.0 and Xamarin.Forms 2.5 support. I will start looking at enhancements now. |
Hi,
By the way, I like using your xfgloss plugin :)
I'm just having issues and I'm trying to bind the value of the color via view model but I guess the plugin doesn't support yet right? :)
The text was updated successfully, but these errors were encountered: