{5} Assigned, Active Tickets by Owner (Full Description) (6 matches)

It appears as if the green channel is missing while writing out png images. This is easy to test in bugplug. I can confirm it is only with png because changing bugplug (in bugplug.cfg) to write 'jpg' files doesn't have the issue. Attached screenshot shows a screenshot of the default castle level.

I haven't tried this bug in 2.0 but it could be present there too.

Migrated from  SFfeat:975687.

Original description:
The stdrep plugin is unnecessarily monolithic and inflexible, and does not mesh well with the original design of the "reporter" mechanism. The original idea behind iReporter was that clients could register any number of iReporterListener objects interested in "listening" for messages. This is a flexible approach since it allows clients to easily install whatever types of listeners they desire. For instance, a listener can log messages to a file, another one can send messages to a remote site, and yet another can emit messages to a HUD in the game.

Unfortunately, stdrep and the iStandardReporterListener interface severely obscure this benefit by trying to do everything at once which anyone might ever want it to do. This makes it overly complex and very inflexible, and does not lend itself to re-use.

A much better approach would be to break down stdrep into several simple, single purpose, very focused components, each of which knows how to do just one thing, and how to do it well. This will allow clients to pick-and-choose properly the components which they want to use (possibly multiple instances of the same component type configured differently).

Obvious standard listener components which should be offered from the decomposition of stdrep include:

- iConsoleOutput emitter

- FILE* emitter (can be used for stdout, stderr, or any real file)

- iFile* emitter

- iNativeWindowManager* emitter (for displaying messages in a native alert panel)

- Jorrit's-Yellow-Box iGraphics2D emitter (for the "yellow box of messages" feature of stdrep)

Of course, clients are free to implement their own iReporterListeners if these standard components do not entirely fulfill their needs.

With the latest version of osx, 10.5.7, the stable static client for PlaneShift has become unusable. Upon investigation, I found that the memory leaks generated by the stable mac client had increased since the previous OS version. For this reason, I have decided to go back to the CS osx files and update them.

The first change I would like to make is to have the main thread's autorelease pool owned by the OSXDelegate class (as opposed to the global autorelease pool currently in place). While the global release pool looks like a good idea theoretically, I believe that the pool is being prematurely released and causing a slew of memory leaks. After making the change in the attached .diff file, I noticed the decrease of a significant number of memory leaks in the PS trunk. The only disadvantage to this change is that our instance of the OSXDelegate will no longer be controlled by an autorelease pool.

If you approve of this change, I will commit it. More suggested updates to follow in the next few days.

~Don Mac