Posts: 719
Threads: 64
Joined: Jan 2013
Another bug report...
I went to edit some CML code on my CQC server.
Opened macro workshop, clicked new session, clicked on any macro.
Got some weird error I didn't write down about macro not loading and the program would exit.
I tired it a few times and got the same results each time. Finally I Restarted CQC service and the problem went away.
--Kill all the serial ports--
Posts: 40,483
Threads: 491
Joined: Aug 2002
That appears to be another one that is unique to you. I've not heard anyone else having this issue. Is this on the same machine as before? And can you load the same macros on the MS?
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
BTW, when you say any macro, I assume you mean ones you wrote, right? Can you create a new one ok? If so, can you then do Ctrl-R and navigate over into the System section and open up some over there?
If so, then perhaps there's something about your macros that is freaking things out. That might explain why it's just this one program that's causing problems for you.
Though, if you can open them on the MS that will point in some other direction so that needs to be tested.
If you can't open your own on the MS either but our macros work fine on either machine, then you can zip up your User macros directory and send it to me and I can try them here to try to find out what is going on. Maybe you managed to get some round about circular import reference or something like that? It shouldn't freak the engine out but I guess it could, and if it started a constant merry go round of downloading and compiling, that could cause weird things to happen.
Dean Roddey
Explorans limites defectum
Posts: 719
Threads: 64
Joined: Jan 2013
Not sure what you mean by "same computer before". I have random issues on both the client and the server. The last issue was on the client.
MS you mean master server? To me CQC server = Master server. So yes.
The macros I was trying to load are the user macros. I didn't think to try other ones.
I don't see how sending them to you would help. The problem disappears when restarting CQC. I don't know how to reproduce it.
--Kill all the serial ports--
Posts: 40,483
Threads: 491
Joined: Aug 2002
Previously you were having issues with the macro WS on the client, but it seemed fine on the MS (master server.) So I'm just wondering if this particular issue (which isn't the same as before) shows up on both machines or just one. If it shows up on both, then it's more likely to be something to do with the macros themselves or the loading thereof. If it only happens on one, then it's more likely something local. So it's an important distinction to know where to look.
As to reproducing it, you indicated it happened multiple times, and I had the feeling you meant it was consistently happening every time you try to load a macro. Is that not the case? Do they work at first and then stop working until you cycle the server?
Dean Roddey
Explorans limites defectum
Posts: 719
Threads: 64
Joined: Jan 2013
Yup, all the macros i selected gave me an error.
No, they didn't work at first. I just logged into the server and it was immediate until restarting the service.
--Kill all the serial ports--
Posts: 40,483
Threads: 491
Joined: Aug 2002
And now they are all working again? If so, then keep and eye on it. If you get it in that condition again, let me know so that we can take a look at what's happening. Of course check the logs to see if the MWS program is spitting out anything in response to trying to load the macros. And definitely try to run the same thing from another machine. That's always a very useful divide and conquer operation, since either way it makes some broad swathes of code more or less suspect.
Do you maybe have any particularly large macros or anything about any of them that might be out of the ordinary? Any possibility of an indirect circular import perhaps?
Dean Roddey
Explorans limites defectum
