Results 1 to 5 of 5

Thread: 4.0.1

  1. #1

    Default Answered: 4.0.1

    I applied the latest update, the grids and trees are still right justified?

  2. The problem should be fixed on the canvas inside the SA. ( unless you are using config rtl: true - in your grid, in that case you will still see LTR ). In the preview you will still see it incorrectly but when you do production build it will be correct.

    As mentioned it's an ExtJS bug, everything will be back to normal once 6.2.1 is out.

  3. #2
    Sencha Premium User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,449
    Answers
    3997

    Default

    This is an Ext JS 6.2 issue not Architect
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Fullstack Engineer
    ________________
    Modus Create is based on the model of an open source team. We’re a remote, global team of experts in our field. To find out more about the work we do, head over to our website.

    Check out my GitHub:
    https://github.com/mitchellsimoens

  4. #3
    Sencha User petr.felzmann's Avatar
    Join Date
    Apr 2015
    Posts
    187
    Answers
    12

    Default

    Erik, can you check your grid is not 'rtl'?

  5. #4
    Sencha User
    Join Date
    Sep 2014
    Location
    Central Europe
    Posts
    795
    Answers
    103

    Default

    The problem should be fixed on the canvas inside the SA. ( unless you are using config rtl: true - in your grid, in that case you will still see LTR ). In the preview you will still see it incorrectly but when you do production build it will be correct.

    As mentioned it's an ExtJS bug, everything will be back to normal once 6.2.1 is out.

  6. #5

    Default

    Quote Originally Posted by petr.vecera View Post
    The problem should be fixed on the canvas inside the SA. ( unless you are using config rtl: true - in your grid, in that case you will still see LTR ). In the preview you will still see it incorrectly but when you do production build it will be correct.

    As mentioned it's an ExtJS bug, everything will be back to normal once 6.2.1 is out.
    The production build has always worked properly for me, my problem has been during development when I publish the site to local web server for testing. In this situation cmd has not done it's magic and the uncompressed files still have the issue.

    I guess the fix I am looking for will be included when Architect has 4.2.1.

    Thanks for your quick response.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •