Jump to content

mig

Administrators
  • Content Count

    87
  • Joined

  • Last visited

  • Days Won

    3

mig last won the day on September 27 2017

mig had the most liked content!

Community Reputation

5 Neutral

About mig

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,674 profile views
  1. Thank you Göran! We'll discuss those enhancements to see how they fit best in our client. Regards, Miguel
  2. Hi Göran, Could you please send me an email to mgonzalez@codicesoftware.com so we can arrange the meeting? Thanks!
  3. Hi @gweronimo, Would you like to discuss your ideas with @S_Luis and me next week? There are some questions we'd like to ask you. We're thinking about next Monday 18 November. What's your timezone? We're UTC+1. Thanks! Regards, Miguel
  4. Hi @Mark Hargreaves, It seems that you moved the client configuration file (client.conf) from your user directory (%LOCALAPPDATA%\plastic4) to the client binaries directory (\Program Files\PlasticSCM5\client). Chances are that your user doesn't have permissions to read or write that file. Could you please check that and give the appropriate permissions to your user? Another alternative would be to copy the contents from C:\Program Files\PlasticSCM5\client\client.conf, remove that file and paste the contents in a new file C:\Users\<your-user>\AppData\Local\plastic4\client.conf . That way, the Plastic SCM client will load it from your local configuration directory and you won't have any additional issues.
  5. Hi guys! Thanks for your feedback. The dynamic layout is still in a really early stage, so we're absolutely open to suggestions and it'll probably change in the future. Answering @SWSBB: yes, this functionality is compatible with manual relayout. Regarding the weights system, I'm happy to tell you that we're already weighting branches according to their relevance in the chart. We're just doing it in a basic way at the moment: main > top-level > parents of workspace branch > workspace branch > children of workspace branch > other branches > integrated branches. We'll take good note of your thoughts on the matter for the next iteration of the dynamic BrEx layout 😉 @jwvanderbeck: I'm afraid yes, the /main branch will always be on top using this dynamic layout. That /main branch always has GUID '5fc2d7c8-05e1-4987-9dd9-74eaec7c27eb', and that's what we move to the top. Then you'll have any other top-level branch beneath it, which might still be useful to you: from what I understand, your /develop branch merges into /main eventually, right? I'll let the team know about your setup to see when we can provide you a way to specify your top-most branch! Thank you so much for your feedback!
  6. Hi all! We're going to release a new feature to make the Branch Explorer diagrams more meaningful. The layout will order branches acknowledging your current workspace status, moving to the top the branches you're more likely to use. We'd love to hear your feedback about this, so we're opening this thread to provide a link in the upcoming release notes when the first layout changes are published. We'll post a new message in this thread when the new feature is released. We can't wait to hear your thoughts!
×
×
  • Create New...