1. #1
    Sencha User
    Join Date
    Mar 2012
    Posts
    106
    Vote Rating
    5
    lgertel is on a distinguished road

      0  

    Default Custom property as boolean

    Custom property as boolean


    Hello!

    I'm trying to add a custom property as boolean, but architect always add a '' inside code.
    Ex.: Adding a property called fullscreen with value true result as fullscreen: 'true' while I want fullscreen: true

    Anyone know how to do it?

    Thanks

  2. #2
    Sencha User
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    50
    Vote Rating
    10
    apsq will become famous soon enough

      0  

    Default


    This annoyed me in ExtDesigner before, but I don't think it has been fixed in Architect as the properties are still stored in JSON.

    You could probably solve this with an override, though this will get tedious if you have a lot of fields like this. In my case I ran into problems with checkboxes having the inputValue "true" and unchecked value "false" submitting their value as strings rather than booleans. My solution was to fix the data prior to submit, though this is by no means the final answer.

  3. #3
    Sencha User
    Join Date
    Dec 2011
    Posts
    17
    Vote Rating
    0
    bionicmaster is on a distinguished road

      0  

    Default


    as a workaround you can edit the metadata of that view for changing property from string to boolean

    Greetings

  4. #4
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,445
    Vote Rating
    129
    aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold

      0  

    Default


    Chances are you should not be marking a component as fullscreen: true. We already do this for the component which is marked as the initial view.

    When you add a custom property, if you specify a type at definition time it will be that type.

    For example
    "fullscreen: true" and then clicking Add
    Aaron Conran
    @aconran
    Sencha Architect Development Team

  5. #5
    Sencha User
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    50
    Vote Rating
    10
    apsq will become famous soon enough

      0  

    Default


    Quote Originally Posted by aconran View Post
    Chances are you should not be marking a component as fullscreen: true. We already do this for the component which is marked as the initial view.

    When you add a custom property, if you specify a type at definition time it will be that type.

    For example
    "fullscreen: true" and then clicking Add
    Seeing how @bionicmaster suggests the type is actually stored in the metadata: any plans on allowing us to specify the type explicitly, possibly via context menu?