Sometimes after a while...

[David Morris]

Hi

None of these are big issues in the sense of causing a loss of productivity with Zeus, but are still a bit of a pain and should be fixed in my view. None of the are apparent when first working with Zeus, and only appear later in the day... Sometimes after a while... (but do occur every day).

1) Maximise: Sometimes, after a while, when a maximised Zeus is minimised, clicking on the icon in the task bar does not maximise the item. Other minimised icons are working correctly at this time. When you right click Zeus normalises (not maximise as you would expect), but doesn't paint completely. Maximising it from the icons in the upper right hand corner of the window puts things back to normal. After that icon be minimised to the task bar and maximised again (normally) until the problem occurs again.

2) Find in files output (xfgrep tool window): Sometimes, after a while, the lines are not parsed correctly if you select a whole line when using 'Open include file' from the right click context menu. How ever if you select the part of the line that includes just the file name of the file name and line number it will open the include file.

3) Right Context: Sometimes after a while, the right context menu shows inappropriate disabled items, these include 'Open Include file', cut copy, and paste. Clicking on a file in the workspace seems to clear this problem.

4) Sometimes when the machine is (very) busy double clicking on a file in the workspace causes the previously highlighted file to open. (Sometimes the new files is not highlighted either - so it looks like the mouse position lags the clicks in some way -- is this Windows?).

I wonder if 1 to 3 are related in some way? None of these bugs occur in any other application as far as I can tell. These problems all occur infrequently, but always each day, sometimes after I have been working for a while, and often if I have been doing something else as well (even just checking email) that involves maximising and minimising windows. I haven't been able to discern a pattern though, and this may be a misdirection.

Regards DM

[jussij]

Hi David,

None of these are big issues in the sense of causing a loss of productivity with Zeus, but are still a bit of a pain and should be fixed in my view. None of the are apparent when first working with Zeus, and only appear later in the day... Sometimes after a while... (but do occur every day).

Be the issue big or small, I am always glad when and any issue is reported

1) Maximise: Sometimes, after a while, when a maximised Zeus is minimised, clicking on the icon in the task bar does not maximise the item.

This sounds a lot like this bug:

http://www.zeusedit.com/forum/viewtopic.php?t=609

Are you running the Zeus Version 3.95v or higher?

2) Find in files output (xfgrep tool window): Sometimes, after a while, the lines are not parsed correctly if you select a whole line when using 'Open include file' from the right click context menu. How ever if you select the part of the line that includes just the file name of the file name and line number it will open the include file.

It is possible the tool output has fooled the open include file feature

How this feature works is it uses a regexp to identify a file name from the line of tool output. It then uses the result of this search to locate the file using the search path. The regexp used either comes from the filename regexp defined in the document type or when this is not defined it uses a set of built-in regexps.

So the problem is the regexp does not always correctly locate a file from the line of output (ie for example files that contain spaces are particularly difficult to identify).

But as you have found, by design, Zeus lets you bypass the regexp search by just selecting the file from the line of output and by doing so the open include generally will have no trouble opening the file.

3) Right Context: Sometimes after a while, the right context menu shows inappropriate disabled items, these include 'Open Include file', cut copy, and paste. Clicking on a file in the workspace seems to clear this problem.

This does sound like a bug

I will see if I can replicate this issue.

4) Sometimes when the machine is (very) busy double clicking on a file in the workspace causes the previously highlighted file to open. (Sometimes the new files is not highlighted either - so it looks like the mouse position lags the clicks in some way -- is this Windows?).

The Windows tree control is quite badly documented so it could well be that Zeus is not quite using it correctly

I wonder if 1 to 3 are related in some way?

Make sure you are always running the latest Zeus patch.

I pretty much have Zeus running non stop for days on end and generally don't see any of these issue.

Cheers Jussi

[David Morris]

Are you running the Zeus Version 3.95v or higher?

I am running 3.95x and I am generally right up to date.

The shortcut command line is:
"C:\Program Files\Zeus395\Zeus.exe" -s -uC:\Work\Montel\Zeus -iC:\Work\Montel\Zeus\zeus32.ini -wC:\Work\Montel\MonTel32.zwi

Naturally, I have a Zeus32.ini this a tad different. I can post/send that if you want? (Note the -s).

So the problem is the regexp does not always correctly locate a file from the line of output (ie for example files that contain spaces are particularly difficult to identify).

But it generally does work. Usually, I am looking a '.c', '.h', '.bat' or '.mak'. They all usually work. And then they ALL don't work, sometimes after a while. Restarting Zeus fixes this.

The Windows tree control is quite badly documented so it could well be that Zeus is not quite using it correctly

Well yes, so true. I found it a real hassle working through that one too. Perhaps try disabling other processing between TVN_SELCHANGING and the END of TVN_SELCHANGED? I had some really weird problems (but can't remember the details) as a result of not doing this. I also did a:

Code: Select all

TreeView_Select(ghTreeView, pNmTv->itemNew.hItem, TVGN_DROPHILITE); 

at the end of TVN_SELCHANGED processing (But again have no idea why now!).

I pretty much have Zeus running non stop for days on end and generally don't see any of these issue.

I am doing some pretty major builds, and I have a rather large project file.

regards DM

[jussij]

I am running 3.95x and I am generally right up to date.

Well there goes that theory

Naturally, I have a Zeus32.ini this a tad different. I can post/send that if you want? (Note the -s).

I generally have just the single Zeus running, but I would have though the -s second instance option would make any difference to how Zeus runs

But it generally does work. Usually, I am looking a '.c', '.h', '.bat' or '.mak'. They all usually work. And then they ALL don't work, sometimes after a while.

That is very strange.

Restarting Zeus fixes this.

It is starting to look like there might be a memory leak in Zeus

Zeus definitely uses a lot of RAM so it is quite possible there is a leak or two hiding somewhere in the code

When this happens next could you take note of the Zeus RAM usage as listed in the Task Manager. If RAM usage is greatly larger than the Zeus startup RAM usage with the same workspace open this might indicate some sort of memory leak.

Perhaps try disabling other processing between TVN_SELCHANGING and the END of TVN_SELCHANGED? I had some really weird problems (but can't remember the details) as a result of not doing this.

I'll take a look at the Zeus tree code and see if I can see any obvious errors.

Cheers Jussi

[David Morris]

When this happens next could you take note of the Zeus RAM usage as listed in the Task Manager. If RAM usage is greatly larger than the Zeus startup RAM usage with the same workspace open this might indicate some sort of memory leak.

Actually, I think that memory usage is a lot more complicated in Win2K (which is what I am using), with the OS doing the occasional defragment, shuffling things around, shoving things out to the disk and so on, so I am not sure task manager will show what you want. (As a test try minimising and maximising Zues with a number of files open). I have the MSDN Process Explode tool, but to be honest I am not quite sure how to drive it. (The version I have Feb 2003) tends to GPF a bit.

regards DM