Not signed in (Sign In)

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentAuthorWyvern
    • CommentTimeNov 5th 2018
     
    I've been mapping using the CA Fantasy Realms template from the 2009 Annual recently. Since (I think) CC3+ Update 18, and still with 19, if I call up the "Select Drawing Tool" window, a number of the sample panes there appear to be blank - that is, there's no sample of what that tool will draw shown in the pane. Some of these are for drawing styles I've amended and saved under new names, but some are those which came with the standard CA template - such as "Terrain Default, Mountain Peak". The same effect also happens with all of the river tool styles, EXCEPT one I amended and saved under a different name!

    The tools themselves are fine. I can click on any and draw with it as normal, and it produces what I'd expect from it, and I can navigate to amending the tool using the "Advanced" button as usual, where that window's sample pane shows again just what I'd expect. So it seems it's just some of the sample panes on the initial Select Drawing Tool window that don't show anything.

    Or is it just me and my system?
    •  
      CommentAuthorMonsen
    • CommentTimeNov 5th 2018
     
    Seems to be a bug with the previews, and it affects much more than just that style. The developer has been made aware, I guess a fix will materialize sometimes in the future.
    It only affects the previews however, and only in that dialog. The previews under "Advanced" and when shown in the symbol catalog are fine, and the tools work fine.
    • CommentAuthorWyvern
    • CommentTimeNov 5th 2018
     
    Thanks, Monsen. Has it just come up during the recent updates, or was I simply mis-remembering that things had been fine before then?
    •  
      CommentAuthorMonsen
    • CommentTimeNov 5th 2018
     
    No, it is a recent problem. It worked under update 17(a).