Bug #23630

-G does not like path reference starting with a backslash

Added by kju almost 4 years ago. Updated over 3 years ago.

Status:Closed Start date:08/21/2011
Priority:Normal Due date:
Assignee:mikero % Done:

0%

Category:MakePbo (Dos Tools)
Target version:-
Affected Version:

Description

Makepbo -G folder says:

Warning E:\#Workspace\ans-promode\dev\TM.Desert_E\features\gdtmod_satchel\CfgSounds.hpp Line 4: \features\gdtmod_satchel\attach.ogg
Warning E:\#Workspace\ans-promode\dev\TM.Desert_E\features\gdtmod_satchel\CfgSounds.hpp Line 10: \features\gdtmod_satchel\settimer.ogg
Warning E:\#Workspace\ans-promode\dev\TM.Desert_E\features\gdtmod_satchel\CfgSounds.hpp Line 16: \features\gdtmod_satchel\starttimer.ogg
Warning E:\#Workspace\ans-promode\dev\TM.Desert_E\features\gdtmod_satchel\CfgSounds.hpp Line 22: \features\gdtmod_satchel\deactivate.ogg

The definition is

class gdtmod_satchel_attach
{
    name = "gdtmod_satchel_attach";
    sound[] = {"\features\gdtmod_satchel\attach.ogg",1,1,10};
    titles[] = {};
};
class gdtmod_satchel_settimer
{
    name = "gdtmod_satchel_settimer";
    sound[] = {"\features\gdtmod_satchel\settimer.ogg",1,1,10};
    titles[] = {};
};
class gdtmod_satchel_starttimer
{
    name = "gdtmod_satchel_starttimer";
    sound[] = {"\features\gdtmod_satchel\starttimer.ogg",1,1,10};
    titles[] = {};
};
class gdtmod_satchel_deactivate
{
    name = "gdtmod_satchel_deactivate";
    sound[] = {"\features\gdtmod_satchel\deactivate.ogg",1,1,10};
    titles[] = {};
};

However arma is fine with \path\to\file.extension in missions.
\path\to\file.extension is the same as path\to\file.extension for missions.

It takes the the mission root as base.

History

Updated by mikero almost 4 years ago

-G for mission space is a work in progress at the moment.

with exceptions (due solely to bis screwups) so called ParsingNameSpace, alias Addon namespace is unconditionally hard-pathed. the \ is assumed and the prefix reference is mandatory. Ie a leading \ is mostly optional, as both are hard prefix paths

missionspace (can) use relative addressing. In the above it is simply that ~features happens to be a child of the root mission folder so that with \without the slash are effectively the same because the file where this text is encountered happens to be in the root mission folder (eg same place as mission.sqm)

move this code to anything in (say) Scripts\ and all bets are off. Features, in this case, would refer to scripts\features (if it existed)

None of which is particularly helpful at moment, the -G option for missions has a long way to go

Updated by kju over 3 years ago

  • Status changed from New to Closed

Works now. ty

Also available in: Atom PDF