Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

307 results found

  1. Sometimes when you modify a file and then rename it, Plastic SCM is unable to match the original file with the renamed one. In that case you can use the ‘Search matches’ tool to select the file that matches the original one. However, It is not always possible, because the minimum similarity level that you can set when searching is 50%.

    Imagine you add a comment to a small file that contains only a definition of an enumerable and then rename the file. Because it is small, the comment becomes a major part of the file and the similarity to…

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hello,

    we have changed the Search Matches form to remove the minimum similarity level. Moreover, we have changed the matching algorithm so that changes in indentation are not taken into account.

    These new features can be found since version 5.0.44.566 of PlasticSCM.

  2. Keep demo server version current with shipping client version so newbies can actually work through the demo.
    update the demo server since the current shipping client is at a new version (5.0.43.0 vs 5.0.44.0)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    The demo server has been successfully updated to version 5.0.44.x, so now you will be able to complete the evaluation guide using the latest PlasticSCM version available. We encourage you to try again and give us feedback of your PlasticSCM experience! :-)

    Thanks!

  3. 127 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. You can only copy text using ctrl-c rather than highlight/select and paste with middle mouse button as in other Linux applications. This is very awkward.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  5. It's been too long in beta, it needs to be released. Some release notes describing how it differs from 4.1 would be nice as well.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  6. While you are doing a code review, you may be interrupted by a call or whatever. It is difficult to keep track of which files you have already verified in that case, especially if the code review is one of many tasks you are performing at the same time :-).

    What do you think about adding a feature of ticking individual files in a code review as verified? Just to know which files you have already seen.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →
  7. Currently, (in "centralized mode") if a server cannot be contacted, the plastic client GUI won't open, even if there are multiple profiles, and another server IS contactable. This appears to depend on the last active workspace - if the last active workspace belongs to the server that is down, the tool can't be opened.

    It would be extremely beneficial to be able to open the tool, and select a different workspace weather the current server is available or not - perhaps show those workspace(s) as greyed out or non-available, disable or close the tabs

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  8. http://i.imgur.com/4OF36ba.png

    this makes the post hard to read - people will TL;DR sooner because you can effectively not scan the article at a glance. One needs to scroll in order to unobscure even the headings

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  9. In the second diagram in "Stop bug spreading" at http://www.plasticscm.com/infocenter/quick-start/intro-task-driven-development.aspx, it says "This check-in introduces a bug, but only "john" will get affected by it until he merges". It was "pat" that made the change, so presumably "john" should read "pat". Either that, or I'm completely misunderstanding the concept.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. The checkin progress dialog just says 'In progess...' with a spinner before 'confirming checkin' starts (eg. when checking dependencies). It would nice if the progress covered all parts of the process since for ~7000 files nothing changes for ~15mins. The subsequent stages where there is a progress bar seem to be much faster (<1min).

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. In the pending changes options there are a lot of checkboxes which hide some specific files from the list of changes.
    It would be nice if those files weren't even scanned through while calculating this view.

    The problem is: we have some data folders inside the workspace with a lot of small files (very slow hard drive access). We need the general option "compair file content not only timestamps". When I click refresh view, with those data folders in my workspace, it takes up to one minute to calculate the view (I have very view data folders, some of my…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  12. When I try to solve a more complex merge I often want to see a diff between an ancestor and a source or between a source and a destination. I know that the merge tool theoretically shows all those diffs at once, but it is not so legible. It would be nice to hide one of the file temporarily and see clean diff between the remaining two only. Or at least open those simple diffs from a context menu in a merge tool, as I can from an "items to merge" list.

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. I think it will be more consistent to highlight (with a darker color) all added characters, even on lines which are all new. See the picture:
    http://s15.postimg.org/uln6ryq17/diff.png
    Otherwise it is more difficult to distinguish what was really changed. Especially for longer lines.

    81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. It is good that now we can navigate through changed/conflicting blocks using arrows even though there is only one changed/conflicting block. However when there is no changed/conflicting block those arrow are just confusing. I suggest to disable them when there is nothing they can navigate to.

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. A commit message text box and a code review text box does not have any scroll bar, does not allow scrolling with a mouse and does not allow Ctrl+A (select all text). All these things would be useful.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. If the entered data are invalid in a new workspace dialog, then a message box appears (which is good) and the dialog is closed (which is bad). Users want to return to the dialog and fix the item, not to fill it again.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. A checkin comments history drop down list is quite narrow and a lot of our comments don't fit there and end with ellipsis. When somebody use two or more comments with a same beginning, he or she cannot differ between them.
    It shouldn't be a problem to make it wider and/or add a popup with the whole text on a mouseover.

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. It is sometimes desirable to to refer to changesets by guid to avoid confusion with replicated repos but if you search for guid (or part of one) nothing is found.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
  20. This sounds odd, I know. But I don't want to have *.dll files in my repository so I ignored them. From time to time though I have some libs that are .dll files which I do want to have in the repository. I could help myself with not ignoring .dll files but the folders they are in, but this doesn't work out very good.

    So what I suggest is a force add or something to add a generally ignored file.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?