flextable background colour issues












1















I am making a flextable using the iris dataset and have noticed an odd issue with the background colour function. I am trying to conditionally colour cells if they are over a certain value:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 5), "green")


enter image description here



It works fine if at least one of the cells satisfies the condition for j, but if non of them do it colours the whole line rather than colouring nothing:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 6), "green")


enter image description here



Is there a way to make it only colour if the condition is met? Also is this a feature or a bug in the flextable package?



Edit:



This has been resolved by version 0.5.1 of the flextable package.






r flextable







share|improve this question




















  • 1





    Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

    – David Gohel
    Nov 29 '18 at 11:19











  • No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

    – RAB
    Nov 29 '18 at 23:13






  • 1





    no problem, I'll answer that question when it will be solved

    – David Gohel
    Nov 30 '18 at 1:18











  • Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

    – RAB
    Jan 31 at 22:00











  • I did not change the selector yet, it will be done in the next run

    – David Gohel
    Feb 1 at 7:40
















1















I am making a flextable using the iris dataset and have noticed an odd issue with the background colour function. I am trying to conditionally colour cells if they are over a certain value:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 5), "green")


enter image description here



It works fine if at least one of the cells satisfies the condition for j, but if non of them do it colours the whole line rather than colouring nothing:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 6), "green")


enter image description here



Is there a way to make it only colour if the condition is met? Also is this a feature or a bug in the flextable package?



Edit:



This has been resolved by version 0.5.1 of the flextable package.






r flextable







share|improve this question




















  • 1





    Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

    – David Gohel
    Nov 29 '18 at 11:19











  • No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

    – RAB
    Nov 29 '18 at 23:13






  • 1





    no problem, I'll answer that question when it will be solved

    – David Gohel
    Nov 30 '18 at 1:18











  • Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

    – RAB
    Jan 31 at 22:00











  • I did not change the selector yet, it will be done in the next run

    – David Gohel
    Feb 1 at 7:40














1












1








1








I am making a flextable using the iris dataset and have noticed an odd issue with the background colour function. I am trying to conditionally colour cells if they are over a certain value:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 5), "green")


enter image description here



It works fine if at least one of the cells satisfies the condition for j, but if non of them do it colours the whole line rather than colouring nothing:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 6), "green")


enter image description here



Is there a way to make it only colour if the condition is met? Also is this a feature or a bug in the flextable package?



Edit:



This has been resolved by version 0.5.1 of the flextable package.






r flextable







share|improve this question
















I am making a flextable using the iris dataset and have noticed an odd issue with the background colour function. I am trying to conditionally colour cells if they are over a certain value:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 5), "green")


enter image description here



It works fine if at least one of the cells satisfies the condition for j, but if non of them do it colours the whole line rather than colouring nothing:



 regulartable(iris) %>%

   bg(i=1, j=which(iris[1,1:4] > 6), "green")


enter image description here



Is there a way to make it only colour if the condition is met? Also is this a feature or a bug in the flextable package?



Edit:



This has been resolved by version 0.5.1 of the flextable package.






r flextable




r flextable






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 8 at 4:41







RAB

















asked Nov 28 '18 at 23:55









RABRAB

1,416418




1,416418








  • 1





    Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

    – David Gohel
    Nov 29 '18 at 11:19











  • No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

    – RAB
    Nov 29 '18 at 23:13






  • 1





    no problem, I'll answer that question when it will be solved

    – David Gohel
    Nov 30 '18 at 1:18











  • Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

    – RAB
    Jan 31 at 22:00











  • I did not change the selector yet, it will be done in the next run

    – David Gohel
    Feb 1 at 7:40














  • 1





    Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

    – David Gohel
    Nov 29 '18 at 11:19











  • No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

    – RAB
    Nov 29 '18 at 23:13






  • 1





    no problem, I'll answer that question when it will be solved

    – David Gohel
    Nov 30 '18 at 1:18











  • Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

    – RAB
    Jan 31 at 22:00











  • I did not change the selector yet, it will be done in the next run

    – David Gohel
    Feb 1 at 7:40








1




1





Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

– David Gohel
Nov 29 '18 at 11:19





Thanks for reporting this. This is a side effect, when selecting none, everything is selected which is a bad idea, sorry. I will correct that but I must be careful (as it may break user's code).

– David Gohel
Nov 29 '18 at 11:19













No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

– RAB
Nov 29 '18 at 23:13





No probs, I have a workaround for now so not needed urgently or anything :) Are you able to post an answer when you release the fix?

– RAB
Nov 29 '18 at 23:13




1




1





no problem, I'll answer that question when it will be solved

– David Gohel
Nov 30 '18 at 1:18





no problem, I'll answer that question when it will be solved

– David Gohel
Nov 30 '18 at 1:18













Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

– RAB
Jan 31 at 22:00





Looks like this has been fixed in the new release, thanks :) one small thing, not all the lines in the table have been removed. Is this by design as well?

– RAB
Jan 31 at 22:00













I did not change the selector yet, it will be done in the next run

– David Gohel
Feb 1 at 7:40





I did not change the selector yet, it will be done in the next run

– David Gohel
Feb 1 at 7:40












1 Answer
1






active

oldest

votes


















1














Issue is now fixed in version 0.5.1 of flextable package






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529890%2fflextable-background-colour-issues%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Issue is now fixed in version 0.5.1 of flextable package






    share|improve this answer




























      1














      Issue is now fixed in version 0.5.1 of flextable package






      share|improve this answer


























        1












        1








        1







        Issue is now fixed in version 0.5.1 of flextable package






        share|improve this answer













        Issue is now fixed in version 0.5.1 of flextable package







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 27 at 2:35









        RABRAB

        1,416418




        1,416418
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53529890%2fflextable-background-colour-issues%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -

            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Image
            0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
            Read more

            Why does System V / AMD64 ABI mandate a 16 byte stack alignment?

            Image
            2 I've read in different places that it is done for "performance reasons", but I still wonder what are the particular cases where performance get improved by this 16-byte alignment. Or, in any case, what were the reasons why this was chosen. edit : I'm thinking I wrote the question in a misleading way. I wasn't asking about why the processor does things faster with 16-byte aligned memory, this is explained everywhere in the docs. What I wanted to know instead, is how the enforced 16-byte alignment is better than just letting the programmers align the stack themselves when needed. I'm asking this because from my experience with assembly, the stack enforcement has two problems: it is only useful by less 1% percent of the code that is executed (so in the other 99% is actually overhead); and...
            Read more

            Firebase ML-Kit Barcode Scanning with Multiple Barcodes

            Image
            0 I'm working on an Android app where the user has to use a camera view to scan a barcode. I've been using Firebase's ML-Kit barcode scanning utility to achieve the actual barcode recognition bit and it's been fantastic. There's only one issue - if given a photo with multiple barcodes in it, it commonly misses at least one of the barcodes. That's problematic because a lot of the barcodes that my users have to scan are on boxes/containers with multiple barcodes. Here's an example Pixel 2 XL box that may need to be scanned: The IMEI barcode in this picture is never picked up by ML-Kit. However; if I crop out everything else and just send the IMEI barcode through ML-Kit picks it up fine. Is there anything I can do to help ML-Kit pick up on all of the barcodes? ...
            Read more