Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Working Copy revert requires close/open in Codea

in Bugs Posts: 290

If I do a revert changes in Working Copy, it seems that I have to close and open the project in Codea before the revert happens. Is that as intended?

Comments

  • dave1707dave1707 Mod
    Posts: 7,388

    @RonJeffries I think it’s a Codea bug. There are other instances where Codea doesn’t update changes that are made. Here’s an example. You can create new tabs and Codea knows they exist, buy you can read them yet. You have to get all the way out of Codea before you can read them.

    function setup()
        lst=listProjectTabs()
        for a,b in pairs(lst) do
            print("tabs  ",b)
        end
    
        for a,b in pairs(lst) do
            str=readProjectTab(b)
            print(b,str)
        end
    end
    
  • SimeonSimeon Admin Mod
    Posts: 4,804

    @RonJeffries hmm this is odd, when I revert a code change in Working Copy with Codea open side-by-side the code in the editor updates to reflect the revert.

    For example, If I create a new tab with a test function, call that function from the main tab, then revert the entire repo I can see the new tab disappear and the code change back to the last commit.

    Did you use the "Setup Synced Directory" feature to get the project into Working Copy? Are all file edits not being propagated through to Codea?

Sign In or Register to comment.