Observed from CCtray to the active project is flagged as 'stopping' others as 'stopped' and they all eventually become 'stopped'. It's just that these projects seem to have no inclination to start running again. I have to do it manually.
When I launch the CC process these projects have a default to be started. On Aug 18, 8:28 am, OBones <[email protected]> wrote: > I'm seeing that too, but they automatically restart right after the > current project has finished building. Or maybe it's right after all > queues are empty. > But clearly, all the projects restart. > Maybe you have a project in progress when you do your change and you > did not wait for it to finish before looking again at your projects. > > On 18 août, 09:14, Spurtus <[email protected]> wrote: > > > > > It seems that when I change the xml configuration of a CC project it > > will stop the project, I then need to remember to start the project > > again through cctray. sometimes I forget / don't notice it is stopped. > > > I make quite a lot of updates to a lot of machines and was considering > > auto updating their configuration every night. > > > However, if projects are liable to stop when a change is picked up > > then I cannot really do this. > > > Is there a way to stop the 'stopping' behaviour when the xml it is > > listening for updates? > > > Best Regards, > > > Spurtus- Hide quoted text - > > - Show quoted text -
