Hi Eric,
I was just diving a bit into the code of LPUB for some other things and I found in the "pli.cpp" the following entries associated with the annotations:
titles << "^Technic Axle\\s+(\\d+)\\s*.*$";
titles << "^Technic Axle Flexible\\s+(\\d+)\\s*$";
titles << "^Technic Beam\\s+(\\d+)\\s*$";
titles << "^Electric Cable NXT\\s+([0-9].*)$";
titles << "^Electric Cable RCX\\s+([0-9].*)$";
My guess is that all parts starting with those strings will be highlighted with their respective length.
Trying..
I can confirm this, as the current NXT cables are called "Electric mindstorms NXT..." and I renamed the parts to fit the LPUB convention and LPUB shows me now the length of the cables in the part lists.
To add now the technic bricks in the current version a line in the code unfortunately would be necessary. May be LPUB should read where to display further info from a settings file?
Gerald
I was just diving a bit into the code of LPUB for some other things and I found in the "pli.cpp" the following entries associated with the annotations:
titles << "^Technic Axle\\s+(\\d+)\\s*.*$";
titles << "^Technic Axle Flexible\\s+(\\d+)\\s*$";
titles << "^Technic Beam\\s+(\\d+)\\s*$";
titles << "^Electric Cable NXT\\s+([0-9].*)$";
titles << "^Electric Cable RCX\\s+([0-9].*)$";
My guess is that all parts starting with those strings will be highlighted with their respective length.
Trying..
I can confirm this, as the current NXT cables are called "Electric mindstorms NXT..." and I renamed the parts to fit the LPUB convention and LPUB shows me now the length of the cables in the part lists.
To add now the technic bricks in the current version a line in the code unfortunately would be necessary. May be LPUB should read where to display further info from a settings file?
Gerald