467 lines
51 KiB
Plaintext
467 lines
51 KiB
Plaintext
{\rtf1\ansi \deff7\deflang1033{\fonttbl{\f0\froman\fcharset0\fprq2 Tms Rmn;}{\f1\froman\fcharset2\fprq2 Symbol;}{\f2\fswiss\fcharset0\fprq2 Helv;}{\f3\fmodern\fcharset0\fprq1 Courier;}
|
|
{\f4\froman\fcharset0\fprq2 Times New Roman;}{\f5\fswiss\fcharset0\fprq2 Arial;}{\f6\froman\fcharset0\fprq2 MS Serif;}{\f7\fswiss\fcharset0\fprq2 MS Sans Serif;}{\f8\froman\fcharset0\fprq2 Times;}{\f9\fswiss\fcharset0\fprq2 Helvetica;}
|
|
{\f10\fswiss\fcharset0\fprq2 System;}{\f11\fmodern\fcharset0\fprq1 Courier New;}{\f12\froman\fcharset0\fprq2 New York;}{\f13\fswiss\fcharset0\fprq2 Geneva;}{\f14\fmodern\fcharset0\fprq1 LinePrinter;}{\f15\froman\fcharset0\fprq2 CG Times;}
|
|
{\f16\fswiss\fcharset0\fprq2 Univers;}{\f17\fswiss\fcharset0\fprq2 Univers Condensed;}{\f18\fswiss\fcharset0\fprq2 Antique Olive;}{\f19\froman\fcharset0\fprq2 Garamond;}{\f20\fswiss\fcharset0\fprq2 CG Omega;}{\f21\fswiss\fcharset0\fprq2 Albertus Medium;}
|
|
{\f22\fswiss\fcharset0\fprq2 Albertus Extra Bold;}{\f23\froman\fcharset0\fprq2 Clarendon Condensed;}{\f24\fscript\fcharset0\fprq2 Coronet;}{\f25\fmodern\fcharset0\fprq1 Letter Gothic;}{\f26\fscript\fcharset0\fprq2 Marigold;}
|
|
{\f27\fnil\fcharset2\fprq2 Wingdings;}{\f28\fnil\fcharset2\fprq2 Marlett;}{\f29\fmodern\fcharset0\fprq1 Lucida Console;}{\f30\fswiss\fcharset0\fprq2 Lucida Sans Unicode;}{\f31\fswiss\fcharset0\fprq2 Verdana;}{\f32\froman\fcharset2\fprq2 MT Extra;}
|
|
{\f33\fswiss\fcharset0\fprq2 Arial Narrow;}{\f34\fswiss\fcharset0\fprq2 Arial Black;}{\f35\fswiss\fcharset0\fprq2 Arial Rounded MT Bold;}{\f36\froman\fcharset0\fprq2 Book Antiqua;}{\f37\froman\fcharset0\fprq2 Bookman Old Style;}
|
|
{\f38\fswiss\fcharset0\fprq2 Century Gothic;}{\f39\froman\fcharset0\fprq2 Century Schoolbook;}{\f40\fswiss\fcharset0\fprq2 Haettenschweiler;}{\f41\fdecor\fcharset0\fprq2 Algerian;}{\f42\fdecor\fcharset0\fprq2 Braggadocio;}
|
|
{\f43\fswiss\fcharset0\fprq2 Britannic Bold;}{\f44\fscript\fcharset0\fprq2 Brush Script MT;}{\f45\fdecor\fcharset0\fprq2 Colonna MT;}{\f46\fdecor\fcharset0\fprq2 Desdemona;}{\f47\froman\fcharset0\fprq2 Footlight MT Light;}
|
|
{\f48\fswiss\fcharset0\fprq2 Impact;}{\f49\fdecor\fcharset0\fprq2 Kino MT;}{\f50\froman\fcharset0\fprq2 Wide Latin;}{\f51\fscript\fcharset0\fprq2 Matura MT Script Capitals;}{\f52\fdecor\fcharset0\fprq2 Playbill;}{\f53\fmodern\fcharset2\fprq1 MS LineDraw;}
|
|
{\f54\fscript\fcharset0\fprq2 Comic Sans MS;}{\f55\fswiss\fcharset0\fprq2 Tahoma;}{\f56\fswiss\fcharset0\fprq2 Abadi MT Condensed;}{\f57\froman\fcharset2\fprq2 Wingdings 2;}{\f58\froman\fcharset2\fprq2 Wingdings 3;}{\f59\froman\fcharset255\fprq2 Roman;}
|
|
{\f60\fscript\fcharset255\fprq2 Script;}{\f61\fmodern\fcharset255\fprq2 Modern;}{\f62\fswiss\fcharset0\fprq1 MS Dialog;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;
|
|
\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}
|
|
{\stylesheet{\li115\ri130\sa48\widctlpar \f7\fs20 \snext0 Normal;}{\s1\li115\ri130\sb80\sa120\widctlpar \b\f7\fs20\kerning28 \sbasedon0\snext0 heading 1;}{\s2\li360\ri360\sb120\sa48\widctlpar \b\f7 \sbasedon0\snext0 heading 2;}{
|
|
\s3\li115\ri130\sb240\sa60\keepn\widctlpar \b\f7 \sbasedon0\snext0 heading 3;}{\s4\li360\ri130\sa48\widctlpar \f7 \sbasedon0\snext0 heading 4;}{\s5\li115\ri130\sb240\sa60\widctlpar \f7\fs22 \sbasedon0\snext0 heading 5;}{
|
|
\s6\li115\ri130\sb240\sa60\widctlpar \i\f7\fs22 \sbasedon0\snext0 heading 6;}{\s7\li115\ri130\sb240\sa60\widctlpar \f7\fs20 \sbasedon0\snext0 heading 7;}{\s8\li115\ri130\sb240\sa60\widctlpar \i\f7\fs20 \sbasedon0\snext0 heading 8;}{
|
|
\s9\li115\ri130\sb240\sa60\widctlpar \i\f7\fs18 \sbasedon0\snext0 heading 9;}{\*\cs10 \additive Default Paragraph Font;}{\s15\li115\ri130\sa48\widctlpar \f7\fs20 \sbasedon0\snext15 footnote text;}{\*\cs16 \additive\super \sbasedon10 footnote reference;}{
|
|
\s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \snext0 Titre Jump topic;}{\s18\li302\ri130\sa48\widctlpar \f7\fs20 \sbasedon0\snext18 Topic Text Indent;}{\s19\li720\ri130\sa48\widctlpar \f7\fs20 \sbasedon0\snext19 Normal Indent;}{
|
|
\s20\li115\ri130\sb80\sa120\widctlpar \b\f7\fs20\kerning28 \sbasedon1\snext0 Tip/Note Heading;}{\s21\li302\ri130\sa48\widctlpar \f7\fs20 \sbasedon0\snext21 Tip/Note Text;}{\s22\fi-187\li302\ri130\sa48\widctlpar\tx302{\*\pn \pnlvl11
|
|
\pnf27\pnfs10\pnstart1\pnindent187\pnhang{\pntxtb n}}\f7\fs20 \sbasedon21\snext22 Tip/Note Text Bulleted;}{\s23\fi-187\li302\ri130\sa48\widctlpar\tx302{\*\pn \pnlvl11\pnf27\pnfs10\pnstart1\pnindent187\pnhang{\pntxtb n}}\f7\fs20 \sbasedon0\snext23
|
|
Topic Text Bulleted;}{\s24\fi-187\li302\ri130\sa48\widctlpar\tx302{\*\pn \pnlvl10\pndec\pnb0\pni0\pnf5\pnfs16\pnstart1\pnindent187\pnhang}\f7\fs20 \sbasedon0\snext24 Topic Text Numbered;}}{\info{\title Help Project generated with RoboHELP\'ae 95.}
|
|
{\author Lhullier vincent}{\operator Lhullier vincent}{\creatim\yr1997\mo4\dy3\hr18\min34}{\revtim\yr1997\mo7\dy23\hr15\min39}{\version30}{\edmins222}{\nofpages40}{\nofwords3530}{\nofchars20123}{\*\company PARTICULIER}{\vern57443}}
|
|
\margl1417\margr1417\margt1417\margb1417 \widowctrl\ftnbj\aenddoc\hyphhotz425\noextrasprl\prcolbl\cvmme\sprsspbf\brkfrm\swpbdr\hyphcaps0\fracwidth \fet0\sectd \linex0\headery709\footery709\colsx709\endnhere {\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang
|
|
{\pntxta .}}{\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}{\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang{\pntxtb (}
|
|
{\pntxta )}}{\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl9
|
|
\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}\pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 {\cs16\super {\*\bkmkstart ROBOHELP}#{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SUMMARY}} {
|
|
\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super $} Vss Data Manager}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Manager; Data; Vss}} {\cs16\super +{\footnote
|
|
\pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0010}} Vss Data Manager
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 This Help file describe how to use the MngData utility which provide simple interface to obtain / update data from a vss data base.
|
|
\par
|
|
\par \{bmc Ico_open.bmp\} {\uldb Requirements}{\v IDH_J_REQUIREMENTS}\line \{bmc Ico_open.bmp\} {\uldb Ini File}{\v IDH_J_INIFILE}\line
|
|
\par \{bmc Ico_open.bmp\} {\uldb Starting with Vss Data Manager}{\v IDH_J_STARTING}\line \{bmc Ico_How2.bmp\} {\uldb How to obtain data}{\v IDH_J_OBTAIN}\line \{bmc Ico_How2.bmp\} {\uldb How to update data}{\v IDH_J_UPDATE}\line \line \{bmc Ico_open.bmp\} {
|
|
\uldb Interface}{\v IDH_J_INTERFACE}\line \line \{bmc Ico_Mark.BMP\} {\uldb Frequently Asked Questions}{\v IDH_J_FAQ}\line \{bmc Ico_Mark.BMP\} {\uldb Questions and Request}{\v {\*\bkmkstart IMAGE}{\*\bkmkend IMAGE}IDH_J_REQUESTS}
|
|
\par \{bmc Ico_Bugs.BMP\} {\uldb Reported bugs}{\v IDH_J_BUGS}\line {\*\bkmkend ROBOHELP}\line
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Logo_1.bmp\}
|
|
\par
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_REQUIREMENTS}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar
|
|
\f7\fs20 {\cs16\super $} Requirements}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Requirements\~; Vss\~; Network}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super +} PAGE_0020}} Requirements
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 First thing you must be connected to the network.
|
|
\par
|
|
\par {\b Time server}
|
|
\par For updating data it is {\b very important} that time
|
|
on all computer is the same. To be sure of that each time you obtain or update data the program synchronize your computer time with time given by a time server. The time server is a little program that run on only a computer and that respond to request do
|
|
ne by the Data Manager. If error with time server appears contact administrator.
|
|
\par
|
|
\par {\b Local path}
|
|
\par In order to obtain data you must define a target local path were obtained data should be written. It\rquote s just a directory in your computer hard disk. It\rquote s name appear in interface window and could be changed.
|
|
\par
|
|
\par {\b Vss database
|
|
\par }You must have access to the VSS database that contains all data you need. So VSS (version 5) must be installed in your personal computer and must have been run at least one time.
|
|
\par Data files are stored in a VSS project, this project is the same for everyone using the same database. Before the utility\rquote
|
|
s main window appears a login window appear, the database ini file is displayed and you can browse to a different Vss database.
|
|
\par You must have right to log to database. Ask your administrator to create to you a login with your name.
|
|
\par By default, when you obtain data all files located in this project and recursively in all sub projects are copied in your hard disk, in the local path you\rquote ve defined.
|
|
\par {\b
|
|
\par }\pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_INIFILE}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Ini File}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Requirements\~; Data\~; Initialization}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +}
|
|
PAGE_0030}} Ini File
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 All initialization data are saved in a file\~located in same directory than the program and which name is {\b MngData.ini}
|
|
. If you open this file you can read in it VSS parameters and other user defined data. If this file is deleted first you loose all your own configuration and most important, you loose system configuration.
|
|
\par
|
|
\par The Ini File can contain these section
|
|
\par {\uldb [Target Path]}{\v IDH_J_SECTIONTARGETPATH} (optional)
|
|
\par {\uldb [Vss]}{\v IDH_J_SECTIONVSS}
|
|
\par {\uldb [FileList-Config##]}{\v IDH_J_SECTIONFILELIST} (optional / ## is a number)
|
|
\par {\uldb [Obtaining]}{\v IDH_J_SECTIONOBTAINING} (optional)
|
|
\par {\uldb [WinPref]}{\v IDH_J_SECTIONWINPREF}(optional)
|
|
\par
|
|
\par {\cf2 To help you understanding the content of this file here is a commented sample. All Ini file line are in blue color if they are optional or in red color if the line must appear in ini file.
|
|
\par }Because there is only one parameter that can\rquote t be edited by the Vss Data Manager here is a sample of a minimal MngData.ini file
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b\cf6 [Vss]\line DataRoot = $\\GameData
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par {\cs16\cf2\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SECTIONTARGETPATH}}{\cf2 }The {\b [TargetPath]} section contains information about folder where obtained data will be written. If this section doesn
|
|
\rquote t exist, file will be copied in your system temp directory.
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cf2 [TargetPath]\line DirName=X:\\CPA\\EXE\\MAIN\\GAMEDATA
|
|
\par }\pard \li115\ri130\sa48\widctlpar {\cf2
|
|
\par }{\cs16\b\cf2\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SECTIONVSS} }The {\b [Vss]} section contains information about VSS.
|
|
\par The \ldblquote DataRoot\rdblquote entry is the most important because it\rquote s the only parameter you can\rquote t edit. This gives the VSS project that correspond to your local directory.
|
|
\par {\i For example if \line TargetPath is X:\\CPA\\EXE\\MAIN\\GAMEDATA \line and Vss DataRoot is $\\GameData \line when obtaining \line $\\GameData\\}{\b\i Options\\Camera.ipt}{\i vss file will be obtain in
|
|
\par X:\\CPA\\EXE\\MAIN\\GAMEDATA\\}{\b\i Options\\Camera.ipt}{\i
|
|
\par }Others entries indicates the last opened database and last user name.
|
|
\par Last parameter which name is FileList indicate your current obtaining file list configuration. It\rquote s automatically manage by the program.
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b\cf6 [Vss]\line DataRoot=$\\GameData\line }{\cf2 DataBase=\\\\Serveur\\VSS5\\srcsafe.ini \line UserName=guest\line FileList=FileList-Config00
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par {\cs16\cf2\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SECTIONFILELIST}}{\cf2 }The {\b [FileList-Config##]} section
|
|
\par .Here is an example of an obtaining file list configuration. For each configuration there\rquote s a name, the number of files or projects to obtain and description of each file / project to obtain. If name is not prefixed, it\rquote
|
|
s a project, if name is prefixed by {\b -R }it\rquote s also a project but content is obtain recursively. Finnaly if prefixe is {\b -F }the name indicate a file that is simply obtain.
|
|
\par There can be as many section [FileList-Config##] as you define File list configuration with Vss Data Manager. These section are automatically written.
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cf2 [FileList-Config00]\line Name=MyConfig\line Number=3\line File0000=-R $\\GameData\\World\\Levels\\_Common\\Families\line File0001= $\\GameData\\World\\Levels\\Cavedoc\line File0002= -F $\\
|
|
GameData\\Options\\Camera.ipt
|
|
\par }\pard \li115\ri130\sa48\widctlpar {\cf2
|
|
\par }{\cs16\cf2\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SECTIONOBTAINING}}{\cf2 }The {\b [obtaining]}
|
|
section contains date and time of your last obtaining. This section appear after your first obtaining. It contains also all files you have obtained.
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cf2 [Obtaining]\line Date= 21/07/1997 14:53\line Number=1\line File0000=-R $\\GameData
|
|
\par }\pard \li115\ri130\sa48\widctlpar {\cf2
|
|
\par }{\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_SECTIONWINPREF}} The {\b [WinPref]}
|
|
section contains saving of window position and size and some options. All this section is optional and created or rewrite each time you quit the program to save the new configuration. Here is a sample of this section
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cf2 [WinPref]\line Main=( 499, 175, 919, 712)\line File=( 489, 247, 899, 691)\line Modif=( 384, 396, 679, 521)\line Conflict=( 537, 50,1218, 450)\line ObtainAfterUpdate=1\line
|
|
ConfirmObtainAfterUpdate=1\line ForceUpdate=1\line ConfirmForceUpdate=1}
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_STARTING}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Starting}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Start, Install, Login}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0050}}
|
|
Starting with Vss Data Manager
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 {\b Installing Vss Data Manager
|
|
\par }At first create a directory to put this utilities (it\rquote s not necessary, MngData5 could be copied anywhere you want.
|
|
\par Copy the 4 following files in the directory you\rquote ve created or anywhere you want
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 \tab MngData5.Exe\line \tab MngData.ini\line \tab MngDtBug.msg\line \tab MngData5.hlp
|
|
\par \pard \li115\ri130\sa48\widctlpar You can create links to MngData5.exe file to access easily the program.
|
|
\par Now you must just change the .ini File to be in order with your database. As explain in topic about {\uldb Ini File}{\v IDH_J_INIFILE} there is only one thing you must write in this .ini file\~:
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b\cf6 [Vss]\line DataRoot = <Your data root project>
|
|
\par }\pard \li115\ri130\sa48\widctlpar Ask your administrator to know what you must write in place of <your data root project>.
|
|
\par
|
|
\par {\b Executing Vss Data Manager
|
|
\par }With explorer go to directory were MngData5 has been installed and double click on MngData5.exe file or use any link you should have created.
|
|
\par A {\uldb login}{\v IDH_J_LOGIN} box appear (select base, enter username and password)
|
|
\par A {\uldb Wait}{\v IDH_J_WAIT} box appear (wait)
|
|
\par \pard \qj\li115\ri130\sa48\widctlpar The {\uldb main window}{\v IDH_J_INTERFACE} appear
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_LOGIN}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Login}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Login, Wait Dialog Box}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0060}}
|
|
Login to Database
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 When running the MngData5 utility first thing to do is to log to Vss Database. To do this administrator must have created an account for you. Ask him if this is not the case or if you don\rquote
|
|
t know username and password of your account.
|
|
\par
|
|
\par To log to the Vss Database use the first window that appears as following
|
|
\par {\i
|
|
\par }\pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_Log.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par In the picture user name and Vss base name are already set. First time you run program the boxes are empty, type your user name in first white box, password in the second one and database name in the third one. To set database name you can use \{
|
|
bmc Bt_VssBa.bmp\} button which offer to browse for the scrsafe.ini file that correspond to the right Vss database.
|
|
\par Next time you run program there\rquote s only the password box that will be empty.
|
|
\par When information are set click OK to log to Vss Database and go forward.
|
|
\par
|
|
\par {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_WAIT}}
|
|
When login is ok, program must initialize some data from Vss database. This operation can take some times if server is used by several people. During all time of this initialization the following window is deiplayed
|
|
\par
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_Wait.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par the line under the picture indicate which vss project is being analyzed.
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_OBTAIN}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Obtain\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Obtain\~; Data}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0100}}
|
|
How to obtain data
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 Here is the procedure to obtain data
|
|
\par
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Running obtaining}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Bt_One.bmp\} Check local path (where data files will be copied)
|
|
\par \pard \li115\ri130\sa48\widctlpar \tab It is displayed in {\uldb main window}{\v IDH_J_INTERFACE}
|
|
\par \pard \li115\ri130\sa48\widctlpar \tab You can change it by using \{bmc Bt_Brows.bmp\} button in main window
|
|
\par \pard \fi605\li115\ri130\sa48\widctlpar and using {\uldb Local path dialog}{\v IDH_J_CHANGINGLOCALPATH}
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmc Bt_Two.bmp\} Define Vss projects and files you want to obtain
|
|
\par \tab By default all files and project will be obtained
|
|
\par \pard \li115\ri130\sa48\widctlpar \tab To set list use \{bmc Bt_More.bmp\} button in {\uldb main window}{\v IDH_J_INTERFACE}
|
|
\par \tab and {\uldb File list configuration dialog box}{\v IDH_J_CONFIGFILELIST}
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmc Bt_Three.bmp\} Click on button \{bmc Bt_Obtai.bmp\}
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar The obtaining procedure is launch, look the result window and progress bar to see if there\rquote s a problem. Data obtaining could be a long procedure if there\rquote s many data files to obtain.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Obtaining algorithm summary}
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Bt_Arrow.bmp\} watch if someone is updating (stop if so)
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Bt_Arrow.bmp\} watch if there still modification in file (if so notify user that obtaining will delete these modification)
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Bt_Arrow.bmp\} synchronize time with time server
|
|
\par \{bml Bt_Arrow.bmp\} notify that someone is obtaining
|
|
\par \{bml Bt_Arrow.bmp\} obtain all wanted data
|
|
\par \{bml Bt_Arrow.bmp\} notify that obtaining is terminate
|
|
\par \{bml Bt_Arrow.bmp\} delete modification file
|
|
\par \{bml Bt_Arrow.bmp\} set obtaining time and files in MngData.ini file
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Obtaining problem
|
|
\par }\pard \li115\ri130\sa48\widctlpar Obtaining could be stopped if
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Bt_Empty.bmp\} time server doesn\rquote t respond. (see administrator)
|
|
\par \{bml Bt_Empty.bmp\} someone is updating (wait the end of updating)
|
|
\par \{bml Bt_Empty.bmp\} you don\rquote t want to delete modification that are still in modification file
|
|
\par \{bml Bt_Empty.bmp\} vss database could not be reached (see administrator)
|
|
\par \pard \li115\ri130\sa48\widctlpar Obtaining could be a very long operation so when you work on a little part of data obtain only the project you are working on. It is better to obtain data when no one else obtain data, because obtaining time w
|
|
hen two person obtain at same time is increase by 5 or more.
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_UPDATE}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Update\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Update\~; Data}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0200}}
|
|
How to update data
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20
|
|
\par Here is the procedure to update data
|
|
\par
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b What is needed
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar you must have {\uldb obtain}{\v IDH_J_OBTAIN} data at least one time
|
|
\par \pard \li115\ri130\sa48\widctlpar you must have modified some data file with 3DOS editors
|
|
\par \pard \li115\ri130\sa48\widctlpar Obtaining time and number of modification appear in {\uldb window interface}{\v IDH_J_INTERFACE}.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Running updating
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar Use \{bmc Bt_Updat.bmp\} button to access Update menu \line \{bmc Mnu_Upda.bmp\} which allow you \line to set some update {\uldb options}{\v IDH_J_UPDATEOPTIONS} by using {\uldb \{bmc Mnu_UpOp.bmp\}}{\v
|
|
IDH_J_UPDATEOPTIONS} menu entry \line or to launch update operation by using \{bmc Mnu_UpUp.bmp\} menu entry
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par Updating result appear in result window and progress bar indicates you process progression.
|
|
\par {\ul It is recommended to re-obtain data after an updating operation
|
|
\par }
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Updating algorithm summary
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \{bml Bt_Arrow.bmp\} watch if someone is updating or obtaining ( stop if so )
|
|
\par \{bml Bt_Arrow.bmp\} synchronize time with time server
|
|
\par \{bml Bt_Arrow.bmp\} notify that someone is updating
|
|
\par \{bml Bt_Arrow.bmp\} update all modified section
|
|
\par \{bml Bt_Arrow.bmp\} notify that updating is terminate
|
|
\par \{bml Bt_Arrow.bmp\} rewrite modification file with modification that generate conflict or error
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\b Updating problem
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par Updating could be stop if
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Bt_Empty.bmp\} time server doesn\rquote t respond (see administrator)
|
|
\par \{bml Bt_Empty.bmp\} someone is updating or obtaining (wait the end of all operation)
|
|
\par \pard \li115\ri130\sa48\widctlpar {\ul Some modification could not be done
|
|
\par }\pard \li115\ri130\sa48\widctlpar this can append when another designer update a section after your last obtaining. This is a case of {\uldb conflict}{\v IDH_J_CONFLICT} because you two have modified section in same time and program can\rquote
|
|
t generally not merge modification. To avoid these delete modification by re-obtaining data, do your modification again under 3DOS editor and update data. There\rquote s no simple solution to conflict problem.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cs16\b\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_UPDATEOPTIONS}}{\b Update option
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par The following window allow you to set some update options
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar
|
|
\par \{bmc Dlg_UpOp.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar First group of options allow you (if checked) to force updating (with or without confirmation) if a {\uldb conflict}{\v IDH_J_CONFLICT} between two files or sections happens.
|
|
\par \pard \li115\ri130\sa48\widctlpar Second group of options allow you to obtain automatically after an updating operation.
|
|
\par
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cs16\b\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_CONFLICT}}{\b Update conflict
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar A conflict appear when you are updating data that was still updated by someone else since last time you have obtained. By default all conflict
|
|
are considered as error. But you can change options (see behind) to force updating in case of conflict. If you have set this option with the confirmation set, each time a conflict happens the following dialog box appears
|
|
\par
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_conf.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par You also can see the two version of the section and the name of the guy that makes the last modification.
|
|
\par You must then choose\~:
|
|
\par \{bmc Bt_Arrow.bmp\} if you want to keep vss file, use \{bmc Bt_Keep.bmp\} button
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmc Bt_Arrow.bmp\} if you want to erase last modification on vss database with you own modification. Use \{bmc Bt_OverW.bmp\}
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_INTERFACE}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20
|
|
{\cs16\super $} Interface\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Interface\~; Dialog}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0300}}
|
|
Interface
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 Here is a description of utility interface. These interface display the program parameters and some buttons to change parameters or run operation.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par Here is a general survey of interface window, show below for a description of each part.
|
|
\par
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_Intf.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par This interface is decomposed in three part,
|
|
\par \pard \li115\ri130\sa48\widctlpar the first one is composed by text box with {\uldb informations and parameters}{\v IDH_J_ITF_INFOS}
|
|
\par the second one is the {\uldb result window}{\v IDH_J_ITF_RESULTWINDOW} (the black window)
|
|
\par the third is the {\uldb command buttons}{\v IDH_J_ITF_COMMANDBUTTONS}.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cs16\b\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_ITF_INFOS}}{\b Informations and parameters
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Itf_LaOb.bmp\}
|
|
\par this line indicate the date and time you\rquote ve obtained data for the last time.
|
|
\par
|
|
\par \{bmc Itf_LoPa.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar This line display local path. This is the directory that correspond to the Vss path. When obtaining all files or sub project found in Vss path will be obtained in the define local path. You can change it by using the \{
|
|
bmc Bt_Brows.bmp\} button and the {\uldb local path dialog box}{\v IDH_J_CHANGINGLOCALPATH}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Itf_VssP.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar You\rquote ll find in this line two information, first one is the Vss project used as root project for data. This information can\rquote t be edited, you must define it when installing the utilities. See description of {
|
|
\uldb ini file}{\v IDH_J_INIFILE} or {\uldb Starting with Vss Data Manager}{\v IDH_J_STARTING} topic for more information.
|
|
\par The second information between bracket is the current {\uldb file list configuration}{\v IDH_J_CONFIGFILELIST} name use \{bmc Bt_More.bmp\} button to change or create new configuration.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Itf_InUp.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
This line display name of vss file used as a semaphore to indicate that someone update, i.e. when this file is checked out that means that someone is being updating and nobody else can obtain or update while this updating isn\rquote
|
|
t finished. This file cannot be changed You can look if someone is being updating by using \{bmc Bt_Look.bmp\} button
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Itf_InOb.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar This line display name of vss file used as a semaphore to indicate that someone obtain, i.e. when this file is checked out that means that someone is being obtaining data and nobody else update while this obtaining isn
|
|
\rquote t finished. This file cannot be changed. You can look if someone is being obtaining by using \{bmc Bt_Look.bmp\} button
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Itf_Modi.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar This two lines indicate the file that contains modification you\rquote ve done since last obtaining with the 3DOS editors\~; and number of modifications. You can delete all modifications by using the \{bmc Bt_Clear.bmp\}
|
|
button and you can display {\uldb modification list}{\v\ul IDH_J_VIEWMODIF} by using \{bmc Bt_View.bmp\} button
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cs16\b\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_ITF_RESULTWINDOW}}{\b Result window
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
This window (with black background) display result of any updating or obtaining operation. Each line indicate a step in operation. The blue lines indicate what is being done, green line indicate a good result for an operation and red lines indicate e
|
|
rrors.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar\box\brdrs\brdrw15\brsp20 {\cs16\b\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_ITF_COMMANDBUTTONS}}{\b Command buttons
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Bt_Refre.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar Use this button to refresh information dumping. You can use it for example if you have edited some data without closing MngData5 utility.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc BT_Obtai.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar Use this button to launch an obtaining operation. See {\uldb How to obtain data}{\v IDH_J_OBTAIN} topic
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc BT_Updat.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar Use this button to display the Update menu that allow you to set some update options or to launch an updating operation. See {\uldb How To Update data}{\v IDH_J_UPDATE} topic
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc Bt_Quit.bmp\}
|
|
\par To quit Vss data manager.
|
|
\par
|
|
\par \{bmc Bt_Help.bmp\}
|
|
\par To access about dialog box or this help file
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_CHANGINGLOCALPATH}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar
|
|
\f7\fs20 {\cs16\super $} Changing local path\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Local path\~; Interface}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super +} PAGE_0350}} Changing local path
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20
|
|
Use the following dialog box to choose directory where data will be obtained. The directory you choose is the root directory of all data, that means that all data files are in this directory or in sub directory of this directory. It correspond to the Vss
|
|
dataproject. For example if vss data project is $\\acp\\Game\\Gamedata and local path is c:\\ed\\Data the file $\\acp\\game\\gamedata\\anims\\ed\\marche.a3d will be obtained and correspond to the file c:\\ed\\data\\anims\\ed\\marche.a3d
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_LDir.bmp\}
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
To change local data path choose the directory you want to be your local path and click ok. You cannot create directory with this dialog box, so use explorer or what you want to do that. Click cancel button if you want to avoid this operation.
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_CONFIGFILELIST}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar
|
|
\f7\fs20 {\cs16\super $} Choosing obtaining project list\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Obtaining\~; Interface\~; Project list}} {\cs16\super +{\footnote \pard\plain
|
|
\s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0360}} Choosing obtained files list
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 When you run obtaining operation you obtain recursively all data files that are in the Vss project. This is the default behavior. With the fo
|
|
llowing interface you can specify what sub project you want to obtain for example if you work on level 2 it gains time to obtain only general data file and level 2 file and to avoid all the other level data files.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_VssF.bmp\}
|
|
\par
|
|
\par \pard \li115\ri130\sa48\widctlpar {\b Step to create a new file list configuration
|
|
\par
|
|
\par }Choose all files / project you want to obtain
|
|
\par Choose a name for your configuration
|
|
\par Click on \{bmc Bt_Ok.bmp\} button
|
|
\par
|
|
\par {\b Step to modify a file list configuration}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par Change file you want to obtain
|
|
\par Click on \{bmc Bt_Ok.bmp\} button
|
|
\par
|
|
\par {\b Choosing files/projects to obtain
|
|
\par }
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
The tree display all files and projects that are on Vss database. You know if a project or file is obtained according to the color of the icon that prefix the file or project name. The legend panel summarize the signification of icons.
|
|
\par \pard \li115\ri130\sa48\widctlpar A project could be prefixed by the following icon
|
|
\par \{bml Ico_PrNO.bmp\} the project will not be obtained
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bml Ico_PrOb.bmp\} the project will be obtained (all files of the project are obtained but not the sub projects)
|
|
\par \{bml Ico_PrOR.bmp\} the project will be obtain recursively ( all files and recursively all sub projects are obtained)
|
|
\par \{bml Ico_PrOC.bmp\} the project will be obtain because it\rquote s a sub project of a project that will be obtained recursively
|
|
\par \pard \li115\ri130\sa48\widctlpar A file could be prefixed by the following icon
|
|
\par \{bml Ico_FiNO.bmp\} the file will not be obtained
|
|
\par \{bml Ico_FiOb.bmp\} the file will be obtained
|
|
\par \{bml Ico_FiOP.bmp\} the file will be obtaind because it owns a project that will be obtained
|
|
\par \{bml Ico_FIOC.bmp\} the file will be obtained because it owns a project that will be obtained recursively
|
|
\par
|
|
\par There is several manner to change obtain state of a file/project.
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmr Bt_ObSta.bmp\}-1- You can select it and use the two bottom left buttons. The text display on these two buttons change following the state of selected item in tree. {\i
|
|
In the example, the selected item is a project that is not obtain, so you can choose to obtain or to recursively obtain it.
|
|
\par }\pard \li115\ri130\sa48\widctlpar -2- Right clicking on a project or file in the tree makes appear a contextual menu that allow you to change state of the clicked project or file.
|
|
\par -3- You can also use the small button that are on legend panel to change state of currently selected project or file.{\i
|
|
\par }\pard \li115\ri130\sa48\widctlpar
|
|
\par There is also two buttons that change all tree obtain state.
|
|
\par \{bmc Bt_ObAll.bmp\} set all file to be obtained
|
|
\par \{bmc Bt_ObNot.bmp\} Just clear the tree by setting all project and file to not obtain state.
|
|
\par
|
|
\par {\b Choose a name for your configuration
|
|
\par
|
|
\par }For this use the \{bmc Bt_Confi.bmp\} button that makes appear the following dialog box
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar \{bmc Dlg_fcfg.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar You create a new configuration by editing a new configuration name in edit box and clicking the \{bmc Bt_Ok.bmp\} button.
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard \li115\ri130\sa48\widctlpar You can also choose an existing configuration. Doing this will reinitialize vss tree with obtained file define in chosen configuration.
|
|
\par \pard\plain \s17\sa240\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_VIEWMODIF}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20
|
|
{\cs16\super $} View modificationlist\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Interface\~; Modification}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super +} PAGE_0370}} Viewing modification list
|
|
\par \pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 This dialog box list all section that have been modified since your last obtaining. Each line in the list box represent one of these modified section. Each line is made like this
|
|
\par \pard \li115\ri130\sa48\widctlpar \tab <filename>[^<sectionid>[:<sectionname>]] (modification type)
|
|
\par
|
|
\par were modification type can be
|
|
\par {\b (modified)}\tab the file/section is both in vss data and local data
|
|
\par {\b (added)}\tab the file/section is only in your local data
|
|
\par {\b (deleted)}\tab the file/section is was deleted from your local data
|
|
\par \pard \qc\li115\ri130\sa48\widctlpar
|
|
\par \{bmc Dlg_ModL.bmp\}
|
|
\par \pard\plain \s17\sa120\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_FAQ}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Frequently asked questions\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} FAQ\~; Questions}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +}
|
|
PAGE_0500}} Frequently Asked Questions
|
|
\par \pard\plain \li113\ri130\sa120\keepn\widctlpar \f7\fs20 see also {\uldb Questions And Requests}{\v IDH_J_REQUESTS}, {\uldb Reported Bugs}{\v IDH_J_BUGS}
|
|
\par \pard \li115\ri130\sa48\widctlpar You could find here the Frequently Asked Questions about Automatic Vss Data Manager.
|
|
\par \pard \li115\ri130\sa48\widctlpar If you have question {\ul contact me}{\v IDH_P_ME}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \pard\plain \s17\sa120\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_REQUESTS}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Questions and requests\tab }} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Questions\~; Request}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +}
|
|
PAGE_510}} Questions And Request
|
|
\par \pard\plain \li113\ri130\sa120\keepn\widctlpar \f7\fs20 see also {\uldb Frequently Asked Questions}{\v IDH_J_FAQ}, , {\uldb Reported Bugs}{\v IDH_J_BUGS}
|
|
\par \pard \li115\ri130\sa48\widctlpar You could find here last Questions and request.
|
|
\par \pard \li115\ri130\sa48\widctlpar If you have question or request {\ul contact me}{\v IDH_P_ME}
|
|
\par \pard\plain \s17\sa120\keepn\widctlpar \b\f4\fs28\lang1024 \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_J_BUGS}} {\cs16\super ${\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {
|
|
\cs16\super $} Reported bugs}} {\cs16\super K{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super K} Bugs\~; Questions}} {\cs16\super +{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super +} PAGE_0520}}
|
|
Reported bugs
|
|
\par \pard\plain \li113\ri130\sa120\keepn\widctlpar \f7\fs20 see also {\uldb Frequently Asked Questions}{\v IDH_J_FAQ}, {\uldb Questions And Requests}{\v IDH_J_REQUESTS}
|
|
\par \pard \li115\ri130\sa48\widctlpar If you find a or several bugs {\ul contact me}{\v IDH_P_ME}
|
|
\par \pard \li115\ri130\sa48\widctlpar
|
|
\par \{bmc ico_abug.bmp\} {\b Can\rquote t update because an edit window appear
|
|
\par }\pard \li115\ri130\sa48\widctlpar This happens when you\rquote ve change editor for displaying file in VSS interface. You must delete this option in VSS interface. To do that open VSS, choose {\b tools} menu and then options {\b sub menu}. In {\b General
|
|
} section delete the editor name written {\i in editor for displaying file
|
|
\par }\pard \li115\ri130\sa48\widctlpar {\i
|
|
\par }\{bmc ico_abug.bmp\} {\b Under Windows95 Help button raised an error}
|
|
\par \pard \li115\ri130\sa48\widctlpar It\rquote
|
|
s another Windows95 mystery. The first time you click on help button an error appear before popup menu is displayed. Close error window, select Help in popup menu another error appear, close again error window, this time program is automatically stoppe
|
|
d. Re-launch it and try Help button, it works ...\~!\~!\~!\~?\~?\~?
|
|
\par \pard \li115\ri130\sa48\widctlpar \page {\b POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP - POPUP
|
|
\par }\page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_LOCALPATH}} {\ul Local path
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name of data root directory.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_BROWSE}} {\ul Browse button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Click this button to change local root data directory{\ul
|
|
\par }\pard \li115\ri130\sa48\widctlpar See also {\uldb changing local directory}{\v IDH_J_CHANGINGLOCALPATH}, {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_VSSPATH}} {\ul Vss data project
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name of vss project that contains all data files.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_MORE}} {\ul More button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Clicking this button allow you to define a list of project you want to obtain. Doing that allow you to obtain only data you work on.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb Choosing obtaining project}{\v IDH_J_CONFIGFILELIST}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_VSSEXE}} {\ul Vss program
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name program used to acess database
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_INUPDATE}} {\ul InUpdate semaphore file
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name of file used as a semaphore file for updating state.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_LOOKINUPDATE}} {\ul Look Update button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Click this button to see if someone is being updating data.
|
|
\par \pard \li115\ri130\sa48\widctlpar \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_INOBTAIN}} {\ul InObtain semaphore file
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name of file used as a semaphore file for obtaining state.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb requirements}{\v IDH_J_REQUIREMENTS}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_LOOKINOBTAIN}} {\ul Look Obtain button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Click this button to see list of users that are being obtaining data.
|
|
\par \pard \li115\ri130\sa48\widctlpar \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_MODIFLIST}} {\ul Modification file name
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the name of file that contains list of modification.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_MODIF}} {\ul Modification number
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the number of modification found in modification file. You can update only when there\rquote s at least one modification
|
|
\par \pard \li115\ri130\sa48\widctlpar \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_VIEWMODIF}} {\ul View modification button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Click this button to view modification list
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb Viewing list of modification}{\v IDH_J_VIEWMODIF}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_OBTAININGTIME}} {\ul Last obtaining time
|
|
\par }\pard \li115\ri130\sa48\widctlpar In this box is displayed the date and time of your last obtaining. If no obtaining has been done the word {\b none }appear in place of date/time
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb How to obtain data}{\v IDH_J_OBTAIN}, {\uldb ini file}{\v IDH_J_INIFILE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_RESULTVIEW}} {\ul Result window
|
|
\par }\pard \li115\ri130\sa48\widctlpar This window display some information about obtaining or updating operation. After each operation look at this window content to be sure that\rquote s no error happens.
|
|
\par \pard \li115\ri130\sa48\widctlpar See also {\uldb How to obtain data}{\v IDH_J_OBTAIN}, {\uldb How to update data}{\v IDH_J_UPDATE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_REFRESH}} {\ul Refresh button
|
|
\par }Click this button to refresh information. If something isn\rquote t good in data you can make change in {\uldb ini file}{\v IDH_J_INIFILE} and then use this button to refresh display.
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_OBTAIN}} {\ul Obtain button
|
|
\par }Click this button to {\uldb obtain data}{\v IDH_J_OBTAIN}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_UPDATE}} U{\ul pdate button
|
|
\par }Click this button to {\uldb update data}{\v IDH_J_UPDATE}
|
|
\par \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_QUIT}} {\ul Quit button
|
|
\par }\pard \li115\ri130\sa48\widctlpar To quit program{\ul
|
|
\par }\pard \li115\ri130\sa48\widctlpar \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_HELP}} {\ul Help button
|
|
\par }\pard \li115\ri130\sa48\widctlpar Use this button to access this help file or to display about box
|
|
\par \pard \li115\ri130\sa48\widctlpar \page {\cs16\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_ME}} \{bmc vlhullier.bmp\}
|
|
\par \pard \li115\ri130\sa48\widctlpar Vincent Lhullier
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmc Ico_Lett.bmp\}\tab {\uldb\cf11 vlhullier@annecy.ubisoft.fr}{\v !ExecFile(MngDtBug.msg, \~, SW_SHOW, IDH_P_MESSAGEERROR )}
|
|
\par \pard \li115\ri130\sa48\widctlpar \{bmc Ico_Tel.bmp\}\tab 04.50.52.98.84
|
|
\par \pard\plain \s1\li115\ri130\sb80\sa120\widctlpar \b\f7\fs20\kerning28 \page {\cs16\fs24\super #{\footnote \pard\plain \s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super #} IDH_P_MESSAGEERROR}}{\fs24 }{\cs16\fs24\super ${\footnote \pard\plain
|
|
\s15\li115\ri130\sa48\widctlpar \f7\fs20 {\cs16\super $} Mail Erreur}}{\fs24 Mail Erreur
|
|
\par }\pard\plain \li115\ri130\sa48\widctlpar \f7\fs20 The file \lquote MngDtBug.msg\rquote not found
|
|
\par in help file directory
|
|
\par } |