Closed Tate83 closed 10 years ago
Interesting... what was the property? I should be pushing some changes in the next few days to use the stuff I've been adding to the engine.
one was an empty stack I tested with after my actual one did not work in 6.1. since it was perfectly fine in 6.0.2. both exporting, I did not really try importing yet
On 3 July 2013 22:37, Monte Goulding notifications@github.com wrote:
Interesting... what was the property? I should be pushing some changes in the next few days to use the stuff I've been adding to the engine.
— Reply to this email directly or view it on GitHubhttps://github.com/montegoulding/lcVCS/issues/1#issuecomment-20443456 .
OK, any chance you could check the value of tProperty when it throws this error?
sure
I made a print screen of all the variables that are assigned in that moment. It seems to be "padding" if I understood your Q correctly.
On 3 July 2013 22:57, Monte Goulding notifications@github.com wrote:
OK, any chance you could check the value of tProperty when it throws this error?
— Reply to this email directly or view it on GitHubhttps://github.com/montegoulding/lcVCS/issues/1#issuecomment-20444598 .
OK, I'll check the properties property because it shouldn't be returning padding for a stack
Ok, seems that the new features are not only positive ;)
Btw, is there a manual how to actually import the Json again? I tried by creating a new stack and pressing import. Or can I just reimport into the original stack to merge changes by others?
Thanks for your quick support! Greez from switzerland
Pascal On Jul 3, 2013 11:13 PM, "Monte Goulding" notifications@github.com wrote:
OK, I'll check the properties property because it shouldn't be returning padding for a stack
— Reply to this email directly or view it on GitHubhttps://github.com/montegoulding/lcVCS/issues/1#issuecomment-20445144 .
Ok, seems that the new features are not only positive ;)
Well... padding is only returned for field so I'm not sure what's going on here
Btw, is there a manual how to actually import the Json again? I tried by creating a new stack and pressing import. Or can I just reimport into the original stack to merge changes by others?
You can drag the .vcs folder onto the GIT icon or if the stack is the current topStack then you can just click it.
Great thanks, that works perfectly fine (in 6.0.2., didn't try 6.1) when I open the backed up .livecode file and import the JSON files.
Is it possible to restore the whole export to an empty stack rather than the existing but out-dated original stack? Would actually allow the really have a team dev environment and recreate the .livecode files "on the fly".
On 3 July 2013 23:22, Monte Goulding notifications@github.com wrote:
Ok, seems that the new features are not only positive ;)
Well... padding is only returned for field so I'm not sure what's going on here
Btw, is there a manual how to actually import the Json again? I tried by creating a new stack and pressing import. Or can I just reimport into the original stack to merge changes by others?
You can drag the .vcs folder onto the GIT icon or if the stack is the current topStack then you can just click it.
— Reply to this email directly or view it on GitHubhttps://github.com/montegoulding/lcVCS/issues/1#issuecomment-20445659 .
Is it possible to restore the whole export to an empty stack rather than the existing but out-dated original stack? Would actually allow the really have a team dev environment and recreate the .livecode files "on the fly".
It does do that... deletes the current loaded one... creates a new stack on the fly. At the moment it sets the filename but doesn't save it to give users a chance to back out easily.
It does do that... deletes the current loaded one... creates a new stack on the fly. At the moment it sets the filename but doesn't save it to give users a chance to back out easily.
Oh, I see. Since I was only able to import when the original stack was loaded I didn't notice. I only saw that a previously deleted button was restored. I'll try to load it into another topstack tomorrow, quick first test wasn't successful.
Great tool btw! :)
I'll close this now that lcVCS 1 is in beta. The padding property being in the properties of a field was an engine issue. The UI is completely different now and based on a lcVCSProject.json file controlling what to import so the other questions probably no longer apply.
Hi Monte,
lcVCS export does not work on 6.1 anymore, it hangs on line 705:
if tObject["properties"][tProperty] is the tProperty of tTemplateObject then with error: stack "lcVCS": execution error at line n/a (Object: object does not have this property)
the same stack exports nicely with LC 6.0.2..
Regards, Pascal