Zugg Software :: View topic - [1.13] Compatibility Report won't display +other import prob

Wizard Joined: 14 Aug 2004 Posts: 1269

For me at least, I can't get the Compatibility Report to display.

The first time it imports my *.MUD file (I imported my chardb.db file I just clicked on my session and pressed Open Offline) it doesn't display as I thought it might based on your blogg, Zugg. OK, no problem there - I guess you didn't have time to implement that yet.

So I open the Package Editor. All I see is the "Default Settings". My mud file is displayed in the Class selector dropdown, but I can't actually get it to show by double-clicking on it or any of the classes it contains (I also tried selecting something and clicking the green tick but that didn't work either). I try selecting the package in the drop-down on the right. That looks like it works but if I click the icon next to it called package properties, it brings up the package properties for the default package, not my mud file. I notice that my mud file is not enabled(!) for the default packages module, so I tick the enable box. Pres Save. Try getting my mud file in the tree again. Still doesn't work. Try the Compatibility Report. Nothing happens.

So I close the Package Editor and re-open it. Bang! My mud is in the tree view! I try to work out what is going on by clicking "Show default packages". There is a flicker of the screen but nothing else happens. No tabs appear at the top like they should (as I discover later). I click on the default package in the class selector at it now shows "(root)". Now it is impossible to go back to my mud file no matter what I try.

So I close the Package Editor and re-open it again. My mud is in the tree view again! Alright, I suppose I know what not to do now. Lets have another go with the Compatibility Report while I can see my imported mud file. Still nothing happens except for a short CPU spike. (The first time I went through this process I think at this point, the wait cursor came up for a while, CPU went right up for quite a while and then finally nothing happened. I am trying to go through this for a second time when I write this post. The first time I managed to do something else after this which caused CMUD to freeze using 100% CPU and I had to kill it after a few minutes.)

Wizard Joined: 14 Aug 2004 Posts: 1269

Ah, I just noticed that if I run the Compatibility Report, alt-tab, alt-tab again but don't let go of the alt-tab keys, so that I can see the window title on the CMUD application it says "Compatibility Report". However, when I let go of alt-tab, I can't find it anywhere, even behind the Package Editor window.

Posted: Mon Nov 06, 2006 9:30 am

Confirmed. I thought it was just me that couldn't pull up the report ( or that my scripts had no detectable errors.)

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I finally got it to display after I clicked for the report three or four times.

When it finally comes up it then has to go through it's little check. Alt tab yes shows it, but before you have clicked it a few times but for me at least alt-tab was to no avail.

After I fixed about half of the compatibility problems the report started to come up after just one try.

Also, BEFORE running the compatibility report none of my alternate trigger or button states were showing. After running the report successfully but not fixing ANYTHING the phantom/missing states returned.

Wizard Joined: 14 Aug 2004 Posts: 1269

Well I have tried to run the Compatibilty Report about 20 times and I've never seen it. Makes it a bit difficult to fix my scripts to get it to display. A vicious circle.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

The first things I fixed all related to replacing & with and and | with or. I have imported my .mud file over from zmud for each version and it usually takes me about a day to get compatibility up to score. The Compatibility report ONCE IT WORKS speeds it up considerably.

So I'd try going through a Ctr-F and looking for ) & ( and ) | (. I know it is tedeous as I have done it for every version since about August.

Also, I edit the session to point to the .mud file open the session offline let it convert; then close the session and open it again. Click the compatibility report. Wait for the processor to slow down, then click it again a few times fast. I know that isn't very exact and it may not work at all.
It just worked for me.

Wizard Joined: 14 Aug 2004 Posts: 1269

There is not much in my scripts that needs changing for compilation in CMUD - I don't use the | or & for OR or AND. I don't use []. I do use, <> so I need to change that. And I'll need to change a fair number of aliases to add parameters, but they compile at the moment with no parameters.

My main problem is that things that should compile don't compile - I've posted another thread on function compile errors.

Posted: Tue Nov 07, 2006 8:23 pm

Not sure why the compatibility report isn't getting displayed for you. I can't reproduce this, but I'll look into it more. Maybe it's opening the window off the edge of the screen or something. I'll add a task-bar icon for the window and see if that helps.

Wizard Joined: 14 Aug 2004 Posts: 1269

Well Arminas got it to display by editing his scripts, it appears. So I wonder if it's an issue with my scripts (and Tech's). Do you still have my *.MUD file and if not do you want me to send you a new copy so you can see if it doesn't display when you load my settings?

Posted: Wed Nov 08, 2006 12:13 am

Looks like the compatibility window doesn't display until it is done checking your scripts. So if you have a large settings file, wait a bit longer. Watch the CPU usage and if it has already dropped to zero, then the window should be somewhere on your screen.

(Actually, what it's doing is first going through your entire set of scripts BEFORE any window is displayed...Then it displays the window and does it all again. So it's actually running the report twice, and no window is displayed the first time)

Wizard Joined: 14 Aug 2004 Posts: 1269

I am waiting for the CPU to drop off. The very first time I ran it, it took quite a long time for the CPU to go down (it was presumably compiling stuff). Now the CPU spikes are only a second long or so.

However, I've just tried the Compatibility Report on the Medieva package that came with 1.13 and it doesn't display for me for that either (even after adding an alias with a #NOOP).

Hope this helps.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I don't know that editing anything made it work. Only that after I had edited things started comming up correctly without having to do the extra clicking.

Posted: Wed Nov 08, 2006 1:56 am

Seb, I'm not sure what to suggest then. I don't get any problems at all with the Medievia package, although maybe some other bug fix that I've already done has caused it to magically start working.

Here is what I just tried with a fresh install of 1.13.

1) From the main session screen, select the pre-defined Materia Magica icon
2) Click on Open Offline
3) Click on the Settings button in toolbar
4) Select Compatibility report from Tools menu.

This displayed the window (with a bunch of complaints about buttons that is a bug). But the window displayed just fine.

So if this isn't working, then there is something wierd with your screen/monitor setup, or something else that is preventing the window from being displayed.

Wizard Joined: 14 Aug 2004 Posts: 1269

For what it's worth, I'm running WinXP SP2, with a screen resolution of 1280x800 (only one screen enabled) and basically the default theme with a few minor tweaks like desktop background and turning off transition effects.

Hmm, so you're saying that the Medievia package actually contains some settings? Because it looks empty to me apart from the alias I created...

I just tried it on the Materia Magica package, and that does contain some settings. However, I still can't see the Compatibility report.

Posted: Wed Nov 08, 2006 5:56 pm

No, the Medievia package doesn't contain any settings at all. That's why the compatibility report comes up instantly for me since there is nothing for it to test. It just comes up and says "No problems found" without any delay.

So, this is really perplexing. You mentioned "only one screen enabled". Do you have a way to use a second monitor to see if the window is being displayed to the left of the main monitor? My system is two-monitors, with the secondary to the left of the main.

Posted: Wed Nov 08, 2006 6:37 pm

If he doesn't I do, which may help, can't do it now, rushing with this so I can go home. Let me know.

Wizard Joined: 14 Aug 2004 Posts: 1269

I have a screen at work that I have occasionally used - I'm on a laptop, so I have a VGA out that I can use to run a second screen. I'll try and test it tomorrow.

Wizard Joined: 14 Aug 2004 Posts: 1269

OK, I have managed to track this one down! Very Happy

If my Package Editor in on my right-hand (secondary) screen when I run the Compatibility Report - it displays on my left-hand (primary) screen when it has finished running. It doesn't matter what screen CMUD in on. If I swap my screens over so the secondary screen is on the left and I run the Compatibility Report from the left (secondary) screen, it still displays on the left screen. If I move the package editor over to the right-hand screen (primary), the Compatibility Report now appears on that screen.

So these are the scenarios:
(a) single screen (but graphics card capable of a 2nd): compatibility report doesn't display
(b) dual screen (primary on the left): compatibility report will only display if you run it from the secondary, right-hand screen, and it displays on the left-hand, primary screen.
(c) dual screen (primary on the right): compatibility report will always display on the same screen that you ran it from.

Enjoy!

Posted: Thu Nov 09, 2006 5:37 pm

Well, that would explain it, because my situation is (c) so thats why it seems to work for me. I don't know why this is only effecting the compatibility window, since I have general routines for handling which screen windows appear on and so this should be happening with other screens too. But I'll disable my second monitor and play with it.

Thanks for testing this and figuring it out.

Posted: Thu Nov 09, 2006 9:03 pm

That mgiht explain my laptop issue. Since I'm on the road, that's the one I use CMUD on. If I get a chance, I'll try it on the home PC.

Wizard Joined: 14 Aug 2004 Posts: 1269

You don't (or at least I don't) actually have to plug in a second monitor to try it out and get it working. Just tick the enable second monitor button in Control Panel, Display Properties, move the 2nd screen over to the left, press Apply (while CMUD isn't running or you get a crash - already submitted), open CMUD and try it. (And try not to lose your mouse cursor!)

Also, CMUD crashed on me on resume from standby since that appears to detect that my second monitor isn't plugged in and disables it, which in turn crashes CMUD.

Wizard Joined: 14 Aug 2004 Posts: 1269

Also, the Compatibility Report currently has stay on top behaviour. You can turn it off, but I'm not sure it should be the default as it's not that obvious to new users how to switch this off.

Posted: Fri Nov 10, 2006 2:20 am

I was able to fix some problems with multiple monitors today.

No, that Stay On Top is needed for that window. With the settings editor it's too easy for the compability window to get hidden behind something else, and since it doesn't have it's own task bar icon, it's easier to lose it than to deal with the stay on top. This is because the Compatibility window isn't "modal". You can leave it open while you click on stuff to view the setting with the problem or view the help file topic, etc. The stay on top allows it to work like a modal window as far as the z-order, but not prevent you from clicking on stuff in other windows. So this is really the way it should work in my opinion.

Anyone who cares will certainly know how to turn off the stay on top option.

Wizard Joined: 14 Aug 2004 Posts: 1269

As I don't have as much screen real estate as you (when only using one monitor) I find I basically switch off Stay On Top (since the compatibility report is obscuring my Package Editor) and have to keep moving the compatibility report around from on the screen to mostly off the screen (but leaving enough so that I can drag it back on the screen) and back again when I want to look at the next script. I think a task bar icon for the compatibility window would be preferable to Stay On Top, but I can live with it how it is.

Wizard Joined: 17 Jun 2006 Posts: 1201

The compatibility window still will not display! When I click to run the compatibility report from Tools, the screen flickers for a couple seconds and it's done. However, all I can see is the button for the window in the taskbar and that's it. I can't maximize the window or get it to show up period. Would be nice if I could right click on the button and click maximize...

Btw...I am running version 1.14