[Gtkradiant] [Bug 446] New: Synapse Problems

gtkradiant@zerowing.idsoftware.com gtkradiant@zerowing.idsoftware.com
Tue, 19 Mar 2002 13:15:37 -0600


http://zerowing.idsoftware.com/bugzilla/show_bug.cgi?id=446

           Summary: Synapse Problems
           Product: GtkRadiant
           Version: 1.3-nightly
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: editor
        AssignedTo: ttimo@idsoftware.com
        ReportedBy: hydra@hydras-world.com


There's something very strange going on with synapse and the loadimage at the 
moment.

I'm doing this (in pluginmanager.cpp):

g_ImageManager.SetMatchAPI(IMAGE_MAJOR, "hlw tga");
g_pParentWnd->GetSynapseClient().AddManager(&g_ImageManager);

I have a SINGLE imagehl.dll file that has two interfaces:

g_SynapseClient.AddAPI(IMAGE_MAJOR, "hlw", sizeof(_QERPlugImageTable));
g_SynapseClient.AddAPI(IMAGE_MAJOR, "tga", sizeof(_QERPlugImageTable));  

and when radiant tries to load "textures/radiant/shadernotex" from a wad file, 
the vfs finds it in "common-hydra.wad", but then CRadiantImageManager::LoadImage
() reports:

WARNING: no image table for extension 'hlw'

even though my radiant.log shows this information:

'imagehl formats module built Mar 19 2002 1.3.2-nightly' activated
RequestAPI 'image' 'tga' from 'imagehl formats module built Mar 19 2002 1.3.2-
nightly' for API 010298A8
RequestAPI 'image' 'hlw' from 'imagehl formats module built Mar 19 2002 1.3.2-
nightly' for API 01029758

Now, here's the weird bit.

if you change:

g_ImageManager.SetMatchAPI(IMAGE_MAJOR, "hlw tga");

to

g_ImageManager.SetMatchAPI(IMAGE_MAJOR, "tga hlw");

there is no problem.

Would someone care to explain this behaviour ?

Also:

gtkradiant\libs\synapse\synapse.cpp(736) : warning 
C4715: 'CSynapseAPIManager::CheckSetActive' : not all control paths return a 
value

it's missing a "return true;" at the end of the function. (I think ?, all other 
paths return false, so i guess it's supposed to return true.)



------- You are receiving this mail because: -------
Whoops!  I have no idea!