I suggest you ...

Add "Update Cloaked" (and "Update Forced") to Items context menu.

If i have items or xlinks specified in cloaked.conf, the only way to force an update of these is to:

* either removed them from cloaked.conf before "Update workspace"

* or run "cm update --cloaked <path>" from the command line.

NOTE: Contrary to old documentation, running the "cm update --forced <path>" command will not update cloaked stuff.

I suggest adding a "Update Cloaked" command to the context menu in the Items view. Maybe also an "Update Forced" command, but this is probably less important.

10 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Göran Wallgren shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Piotr Mis commented  ·   ·  Flag as inappropriate

        I would propose to add it rather as sub-option of "Update workspace" button in "Item" tab.
        This buton shall behave in the same way as "Check-in" button on "Pending changes".

        In this way you do not overload menus.

        Generally I am downloading cloaked files during build preparation as they are changed and checked-in after build.
        I recall that I have some problems when I did not uncloaked these files and tried to check-in new versions.

      • Göran Wallgren commented  ·   ·  Flag as inappropriate

        Yes it's big, but I suggest you could hide more menuitems based on context (just as you do with the "Create Xlink..." item) :

        * "Add to source control" need not be visible for Controlled files.
        * Submenu "Open" for directories could be replaced with single menuitem "Open in Windows Explorer".
        * Submenu "Change revision type" need not be visible for directories.
        * Submenu "New" need not be visible for files.
        * Submenu "Annotate" need not be visible for directories.
        * ("View history ..." could be a submenu.)
        * Submenu "Search" need not be visible for files.

      • psantosl commented  ·   ·  Flag as inappropriate

        I'll see what we can do :-)

        But look at the items menu... it is already way too big :-S

      • Göran Wallgren commented  ·   ·  Flag as inappropriate

        Menu will not be overloaded since this option need only be visible on cloaked items.

        Common or not, we should not have to resort to CLI for this. After all, yours is the best SCM out there.

      • psantosl commented  ·   ·  Flag as inappropriate

        Thanks Göran,

        We're always concerned of overloading the menus with too many entries (and IMO there are already too many in the items view).

        Frankly, this is not a common scenario: normally cloaked content stays cloaked and updating it is not frequent (or at least it shouldn't be), so we think the CLI is good enough for this.

      Feedback and Knowledge Base