Skip to content

Settings and activity

4 results found

  1. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Git bisync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jordan Pickwell commented  · 
    Jordan Pickwell supported this idea  · 
    An error occurred while saving the comment
    Jordan Pickwell commented  · 

    PSCM 5.0.43.483, and above, support a gitsync.conf file. Not sure what the format is.

  2. 4 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  ·  Git bisync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
  3. 44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Git bisync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jordan Pickwell commented  · 

    Another option could be to support .gitignore in-place of ignore.conf.

    Jordan Pickwell supported this idea  · 
  4. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jordan Pickwell supported this idea  · 
    An error occurred while saving the comment
    Jordan Pickwell commented  · 

    You can't fit both horizontally and vertically because that would imply that you could change the aspect ratio of the view, which you can't. So, "Fit on Screen" would choose the better of the two; whichever fits the most information on the screen.

    The auto zooms would respect the minimum and maximum zoom levels. So, if you try to "Fit Horizontally", but the branches are too long to fit on the screen even if you zoom out completely, then that's what the option does, zooms out to the minimum zoom level.

    The inverse is also true; if you take a new repo and view it in the BrEx, then "Fit Horizontally" or "Fit Vertically" might zoom in to the maximum zoom level.

    These operations have to also respect the size of the view area in relationship to the user's screen resolution. From a .NET/Mono perspective, the auto zooms respect the size of the BrEx control's client rectangle.

    An error occurred while saving the comment
    Jordan Pickwell commented  · 

    "Actual Size" would reset the zoom of the BrEx to the default value.

    "Fit Horizontally" would try to fit all the branches within the width of the BrEx.

    "Fit Vertically" would try to fit all the branches within the height of the BrEx.

    "Fit on Screen" would try to fit all the branches within the client area of the BrEx. The same as using "Fit Horizontally" and "Fit Vertically".

    Look at Photoshop, Windows Photo Viewer, Windows Live Photo Gallery, and others, they all have an "Actual Size" zoom and a "Fit on Screen" zoom. In text editors that have zoom capabilities, there's always a "Reset Zoom" option to bring the text back to 100%.

    It would also be nice to have a zoom indicator at the top or bottom that shows the current zoom level, similar to MS Word or maybe like Photoshop's.

    Jordan Pickwell shared this idea  ·