4 réponses à ce sujet

[johnbgardner]

Up until recently, I've had no trouble with the custom .tlk associated with my module.  I added some toolset categories to help organize the toolset and now, even though I didn't change the name or location of the .tlk, the module doesn't see it at all.  I've tried disassociating and saving, then adding the .tlk again to no avail.  The .tlk loads into TLKEdit2 fine and saves without error, so I'm totally at a loss as to what's going wrong.  Does anyone please have an idea what the problem might be?  Thanks muchly.

[johnbgardner]

Ok, update on the problem. The module is in fact loading the .tlk, but the string references called by the blueprints aren't showing up. I loaded the conversation editor and tried to edit a reference to the custom .tlk and it showed up properly. It's just that the blueprint categories I'm calling from the .tlk are appearing blank. Anyone have any ideas?

[Morbane]

what numbering are you using?

1, 2, 3, etc

or

166677012 (or something like that )

[Dann-J]

Are the blueprints in the module itself (showing up as bold text), or are they in a HAK or the override folder? Since the TLK file is associated with the module, it might be that only local module blueprints can access it.

[johnbgardner]

Ok, it's figured out. It appears that dialog.tlk is loaded with the toolset. Opening a module loads the blueprints FIRST, then the custom .tlk, so any strings in the custom .tlk needed by the blueprints have no reference. I'm either going to have to modify the dialog.tlk (absolutely NOT recommended) or resign myself to hard-coding the category strings in order to maintain the organization I desire. *sigh*. Not really a problem, but a slight nuisance nonetheless. Thanks for the replies all, but it appears BW didn't take customization of the toolset into account when they programmed the loading sequence.