How and why to use Content Presenters in WPF

Поделиться
HTML-код
  • Опубликовано: 30 окт 2024

Комментарии • 21

  • @sanjaityagi4295
    @sanjaityagi4295 9 лет назад +3

    I haven't seen any simpler and better explanation ... Thanks a ton !!!

  • @Giri891
    @Giri891 9 лет назад

    Great video Brad. Very simple and easy to understand

  • @tammarinwonderland1
    @tammarinwonderland1 6 лет назад

    Great video, just what I needed.

  • @BradCunningham
    @BradCunningham  11 лет назад +2

    Glad to hear it helped.

  • @nayansoni21
    @nayansoni21 11 лет назад

    Thanks for sharing.. Really cleared my doubts on ContentPresenter. Thumbs Up !!

  • @solvedplus858
    @solvedplus858 2 года назад

    very nice, thanks

  • @ramiyamable
    @ramiyamable 11 лет назад

    Thank you. Very didactic explanation

  • @bogdanchlebowski5626
    @bogdanchlebowski5626 10 лет назад

    Thank you for your video very instructive. What to do to change template on button press. Should I use VisualStateManager or Triggers ? What is the best practices

    • @BradCunningham
      @BradCunningham  10 лет назад +1

      Hi Bogdan,
      I am personally a fan of Triggers but they are WPF specific (does anyone even care about silverlight any more...) But the VSM is also an option. The only advice I have is, if they change you are making is a non animate-able property than triggers work better otherwise you could use either (Triggers or VSM) again, I prefer triggers as I think they are simpler.

  • @HerbertNijkamp
    @HerbertNijkamp 3 года назад

    Great video and explanation Brad, even when the video is old. But still I have a question. When I have multiple pages and want to use the same templates on all pages, do i have to copy/past them to all pages or is there also a higher level where I can put the general purpose templates to and then simply use them in all the WPF Pages for that project?

  • @ssaqibalitipu
    @ssaqibalitipu 8 лет назад

    Hi Brad, first of all your videos are awesome, thanks a lot for sharing. Now coming to my question. I know that TemplateBinding by default assume control type as Control and binding to content shall raise error do make sense. Setting TargetType takes care of this. But I am surprised to see it works for you. Is this implementation changed later as for me without setting TargetType it gives error.

    • @ssaqibalitipu
      @ssaqibalitipu 8 лет назад

      To avoid confusion i meant the first attempt - binding contentcontrol content to button content using template binding.

    • @BradCunningham
      @BradCunningham  8 лет назад

      +Syed Saqib Ali Tipu it worked because the template is nested inside the button element directly as opposed to being in a resource. the editor can tell what the target type is when the template is nested under it directly. hope that helps.

  • @swoyum
    @swoyum 11 лет назад

    clear !

  • @wind7489
    @wind7489 9 лет назад

    Огромное спасибо) Именно то, что я искал.

  • @adhoom
    @adhoom 6 лет назад

    Awesome work. But you should improve your typing speed

  • @ivandrofly
    @ivandrofly 2 года назад

    1:59 ContentControl and ContentPresenter

  • @sumitagarwal2468
    @sumitagarwal2468 8 лет назад

    I have spent more than 4mins , i didnt understood contentPresenter .

  • @Amine-gz7gq
    @Amine-gz7gq 4 месяца назад

    wpf is really an awful technology