Welcome to TalkGraphics.com
Results 1 to 2 of 2

Hybrid View

  1. #1
    Join Date
    Apr 2012
    Location
    SW England
    Posts
    17,830

    Thumbs down v16.1 - Unexpected Results with default Group

    Dear Xara...

    Up to now, I have been able to group objects and give them a Name ("name", htmlclass="name", filename="name").
    This fails messily if you do not remember to choose the new feature of Web Properties > Image > Group images: One image for the whole group.
    Surely, this ought to be the default.

    To take a case study where I created a ringed play button of a ring and a triangle, I grouped both and ensured the group had a Name of filename="play"; I also had to set the Web image type to PNG to ensure the transparency.
    The same design file in v16.1 "assumes" Group images of Separate images for group members and also removed the PNG choice.

    The Names display simply states "There is one group selected" regardless of the new Group image choices.
    The information here needs to be improved.

    Simple Names will be readily broken as will classes.

    Acorn
    Acorn - installed Xara software: Cloud+/Pro+ and most others back through time (to CC's Artworks). Contact for technical remediation/consultancy for your web designs.
    When we provide assistance, your responses are valuable as they benefit the community. TG Nuggets you might like. Report faults: Xara Cloud+/Pro+/Magix Legacy; Xara KB & Chat

  2. #2
    Join Date
    Aug 2000
    Location
    Harwich, Essex, England
    Posts
    21,919

    Default Re: v16.1 - Unexpected Results with default Group

    Web Properties > Image > Group images: One image for the whole group.
    Surely, this ought to be the default.
    Couldn't agree more. Up until recently grouping one, two or more shapes converted these to a single bitmap image. With this release this behaviour has changed drastically. Not only do you need to group the shapes but select the above step to ensure a single image. However as it's not set as the default it now must be included as an additional important step especially if you're creating your own buttons / navbars. For users used to the previous behaviour this will create very odd results.

    16.1 should have been released with the default reversed, otherwise the results are definitely not WYSIWYG
    Last edited by Egg Bramhill; 05 March 2019 at 10:07 PM.
    Egg

    Intel i7 - 4790K Quad Core + 16 GB Ram + NVIDIA Geforce GTX 1660 Graphics Card + MSI Optix Mag321 Curv monitor
    + Samsung 970 EVO Plus 500GB SSD + 232 GB SSD + 250 GB SSD portable drive + ISP = BT + Web Hosting = TSO Host

 

 

Bookmarks

Posting Permissions

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