Bioinformatics.org
[OMICtools]
Not logged in
  • Log in
  • Bioinformatics.org
    Membership (40732+) Group hosting [?] Wiki
    Franklin Award
    Sponsorships

    Careers
    About bioinformatics
    Bioinformatics training
    Bioinformatics jobs

    Research
    All information groups
    Online databases Online analysis tools Online education tools More tools

    Development
    All software groups
    FTP repository
    SVN & CVS repositories [?]
    Mailing lists

    Forums
    News & Commentary
  • Submit
  • Archives
  • Subscribe

  • Jobs Forum
    (Career Center)
  • Submit
  • Archives
  • Subscribe
  • BIRCH: Comprehensive bioinfo. system - Support tickets

    Submit | Open tickets | Closed tickets

    [ Ticket #1158 ] Paste overwrites sequences
    Date:
    10/12/11 12:50
    Submitted by:
    B_Fristensky
    Assigned to:
    Alvare
    Category:
    bioLegato
    Priority:
    7
    Ticket group:
    Bug
    Resolution:
    Resolved
    Summary:
    Paste overwrites sequences
    Original submission:
    There seems to be an "issue" in 0.7.7a with cut and paste.
    Try reading in the GenBank sequences from the sequence tutorials.

    Select PBI101TD.
    Cut
    Select X52331
    Paste
    PBI101TD gets pasted, replacing X52331.

    In GDE, the behavior, I think was to insert the pasted sequence at the site of selection, pushing the others
    down one row. If all sequences are deselected, the paste is done below the bottom sequence.

    I can see that the "right" way to do this is to make a
    New sequence, and past into the new sequence. However,
    people are used to pasting into an insertion point in text documents, and we have no way of specifying that in bioLegato. It didn't immediately occur to me that I needed to create an empty sequence as a target for a paste. This becomes especially
    inconvenient if I want to cut and paste a block of sequences.

    One possibility is to prompt the user, asking if they really want to overwrite the target sequence. However,
    I am finding it hard to imagine a situation in which
    one would want to overwrite one sequence with another. By the same token, it is potentially dangerous to past over
    an existing sequence if you didn't expect it.

    My suggestion then is to go with the GDE style behavior of pushing the others "down" from the insertion point. And if you really want to delete sequences, that's done
    as a deliberate cut step.

    Can you think of a better way?


    Please log in to add comments and receive followups via email.
    Followups
    Comment Date By
    This bug has returned in bioLegato.0.7.9

    08/29/12 18:03 B_Fristensky
    No results for "Dependent on ticket"
    No results for "Dependent on Task"
    No other tickets are dependent on this ticket
    Ticket change history
    Field Old value Date By
    status_id Open 09/22/12 14:00 B_Fristensky
    resolution_id Not Resolved 09/22/12 14:00 B_Fristensky
    close_date 12/28/11 16:23 09/22/12 14:00 B_Fristensky
    status_id Closed 08/29/12 18:02 B_Fristensky
    resolution_id Resolved 08/29/12 18:02 B_Fristensky
    status_id Pending 12/28/11 16:23 B_Fristensky
    close_date 12/31/69 19:00 12/28/11 16:23 B_Fristensky
    resolution_id Not Resolved 10/31/11 11:37 Alvare
    priority 5 10/12/11 12:51 B_Fristensky
    assigned_to unset 10/12/11 12:51 B_Fristensky
    resolution_id Unset 10/12/11 12:51 B_Fristensky

     

    Copyright © 2019 · Scilico, LLC