Using RadImageEditorUI problems

4 posts, 0 answers
  1. Christie Admin
    Christie Admin avatar
    239 posts
    Member since:
    Aug 2013

    Posted 07 Jul 2015 Link to this post

    Hi,

     

    in my usercontrol I'm trying to use a RadImageEditorUI and when I try to compile I have the following message:

    Error 7 The type or namespace name 'Windows' does not exist in the namespace 'ChristieInnoMed.Framework.UI.Telerik' (are you missing an assembly reference?) D:\Developpement\TFS\ChristieInnoMed.Framework\ChristieInnoMed.Framework.UI.ChristieControls\Controls\SketchDrawer.xaml 13 26 ChristieInnoMed.Framework.UI.ChristieControls

     If I comment the "<telerik:RadImageEditorUI x:Name="ImageEditorUI" />" line, the compile was ok...

     

    Thank's

    Alain


  2. Anna
    Admin
    Anna avatar
    99 posts

    Posted 08 Jul 2015 Link to this post

    Hi Alain,

    Thank you for your question.

    Unfortunately, the cause of the issue is not obvious from the error message. Can you please double check if you have added the correct assemblies? You can find a list of those in our Getting Started article on the RadImageEditor. Also, please make sure you are using the correct namespace in your XAML.


    If all of those are in order, can you please prepare a sample solution for me which demonstrates the error?

    Regards,
    Anna
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for WPF is Visual Studio 2017 Ready
  4. Christie Admin
    Christie Admin avatar
    239 posts
    Member since:
    Aug 2013

    Posted 20 Jul 2015 in reply to Anna Link to this post

    I Anna,

    in my current project, removing the "x:Name=..." solved the issue.... Do you know why it occur???

     Thank's

    Alain

  5. Todor
    Admin
    Todor avatar
    168 posts

    Posted 23 Jul 2015 Link to this post

    Hi Alain,

    Removing the x:Name attribute from the control can fix the issue if in the same scope there is another control defined with the same x:Name. However, I cannot conclude what cause the issue only by the provided error. 

    If you can isolate the problem in a sample project where it can be reproduced, please send it to us. In this way, it will be much easier to find what might cause the issue and solve it.

    Regards,
    Todor
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top