During the save/tags update process, rarely more than 2%. During a rebuild, 2-3% bouncing up to 7-8% toward the very end.

I guess I'll just leave all the update options off for now.

Bill

The memory consuming behavior is back. When I save the file, the memory footprint grows by a progressively larger amount.

For example, right now it's 76.9, the 78.0, 78.8, 81.9, 89.4, 101.1, 120.5, 152.6, 204.5, 288.1, 426.5, 646.4, 1005.6. Each time I am pressing only Ctrl-S, and waiting until ...

I ran similar tests on Windows 7 and Windows XP, and I would agree with your conclusions there. On Windows XP, I saw virtually no change, in fact memory footprint seemed to cycle up AND down. On Windows 7, I say an increase of about 50K with each cycle.

I then returned to the Windows 8 machine to ...

Nope, the files are all on the local machine. My machine has an SSD C drive and 2 SATA drives as E and F. The files are all actually on E:, but there is an NTFS junction from C: that points to the E: drive, so you can see the same files/directory structure using C: or E:. The junction thing is ...

It looks pretty definitely like the tags update process. When I turn the update on save option off for the workspace, I can save files repeatedly with no impact on the memory footprint. I tried it about 30-40 times, and saw no change in the memory usage. When I turned the update on save back on, I ...

It does appear that there is a major memory leak going on, probably with the tag update process. Every time I save a file, the memory usage as shown in task manager jumps. It also appears that the amount by which it jumps is growing each time. For example, I'm now at 194.8Mb, saving jumps to 281.3 ...

Does Zeus have any known issues with Windows 8? I am running 3.97o and have had a couple of problems, including messages about internal errors, and another regarding having used all of the 2GB address space. There is some chance that I brought this on myself by running Zeus both native Windows 8 and ...

OK, guess I didn't try quite hard enough. My mistake seems to start with assuming that I needed to use the Shift key to select - that doesn't appear to work, but I can now mark columns using the arrow keys alone. Thanks.

Is there a way to select a rectangular block using the keyboard? It's easy enough to do with the mouse, but not always very convenient. I can't find any significant difference between column marking and block marking using the keyboard. What I'd like to be able to do is to select a few columns on ...

So with Errors, the coloring is applied to the entire line without the ability to color individual words on the line? That's what I'm seeing.

For me, the ability to use the error navigation functions (CompilerErrorNext, etc.) outweigh the advantages of coloring, but it would be nice to have both ...

Whoops, a little too hasty. Actually, removing the error regex has some undesirable side effects - Zeus no longer thinks the compile has any errors, so displaying the error messages doesn't work anymore. The cursor is then positioned on the first output line instead of the first error message - that ...

Thanks, that did the trick. I actually ended up with the Compiler Output View coloring instead of Tool Output View, but that was the clue I needed.

I also discovered that the Errors coloring appears to take precedence - I had a errors regex defined for the source document type and it was applied ...

Is there any way to do text coloring in a tool window? I've got compiler error output like this:


C:\code\Peterson\qsys.lib\LPUSR500.LIB\QLBLSRC.FILE\PCC1810.CBL (376) * 3091 MSGID: LBL0600 SEVERITY: 10 SEQNBR: 037600 No INPUT fields found for format PC41810201.
C:\code\Peterson\qsys.lib\LPUSR500 ...

Hi, Jussi

The SearchNext() did the trick.

Do all of the keyboard functions return some kind of success indicator or is it just selected ones? I don't find any indication that any of them, including SearchNext() return any sort of value. Is this is just a documentation issue?

Hi, Jussi,

Some additional info: I thought to copy the line to a new file then run the ReplaceNext there. That works every other time.

What I did was to copy a single matching line, then open a new document and paste it in. When I then run my test macro with the ReplaceNext(), it works. If I undo ...