[X] My Assistant

[vk3ukf]

Hi Kevin,

Nice and extensive program that you've written!
But whew! There are many of those *.pas files. Which of them would you recommend?
And then I have probably no clue how I could "it" let run along with my JavaScript

Anyway Thanks!

Hi Tman, yeah there is a few, this file has most of the interesting code in it.

MerViewer20071Unit1.pas

This is the code for the main view page, this does the dates etc.

If you see codes for buttons e.g.
Button3.Click; may be mentioned as doing some feature, say for example clicking on button 3 will show page 4, such code as,
Form4.Show;
Look for the file ending in ***Unit4.pas and the appropriate code will be in there.
I tried to name the *.pas files for what they did, a couple got mucked up.

So, the command Form4.Show; will display the 4th page created which has some name ending in Unit4.pas, the UnitX.pas at the end really helps during wandering while trying to match statements.

Program pages are in fact called by statements such as Form9.Show;
Which will show the 9th page I made.
Which will have a *.pas name ending in ****Unit9.pas or ****Unit20079.pas

Last year I put the actual year into some of the filenames, so if you see e.g. PageFunctionNameUnit200735.pas, remove the 2007 bit in your mind, it is really PageFunctionNameUnit35.pas or page 35.

I know what you mean when getting into other languages, I'm there when I look at Java.
I've had a little success myself in playing around a tad with Java, but my candle is dim.

Just ask Tman, I'll do my best.

Java and other high level languages can usually be interpreted fairly well, they are not too disimilar.

Me changing file naming protocols midstream is another thing that needs to be rectified, this happened after a crash and recovery.

All I was concerned about at the time was getting it all to compile, again.

If there is some thing in the executable you were interested in, ask, and I'll point you to the page with the relevant code in it.

Kevin.

P.S. the executable in the download has a visible Phoenix button at the lower right, not yet fully functional, but will be invisible once auto spacecraft ID is implemented using the filenames.

P.P.S. any comments or non functional code that is ignored by the compiler begins with a double forward slash //

Here is a list of the units used by Form 1, the main page.

StereoUnit20072, TimeVariablesUnit20073, WebLinksUnit20074, VK3UKFCalendarUnit20075,
TraverseMapsUnit20076, FullSizeUnit20077, DataDecodeUnit200710,
StereoManualSelectUnit200711, MoreInfoUnit200712, MSTspUnit200713, OtherTravUnit20078,
SpiritTravUnit20079, ClosingCreditsUnit200715, SldShwDlyUnit200716, FullSizeImageUnit200717,
HelpUnit200718, ColourUnit200719, ColourAltUnit200720, SunsetUnit200721, WorkPadUnit200722,
SOLsearchUnit200723, BirthdaySearchUnit200714, RegistrationUnit200729, TestingUnit200730,
MsgUnit200731, MarsLnksUnit200724, UnitREG200732, MarsWebLnxUnit200734,
SolrSysLnxUnit200735, MeteoritesLnxUnit200736, HAMLnxUnit200737,
ParticipateUnit200738, AVIUnit200740, Mag2007Unit42, ClipboardSeeUnit43,
Watermark2007Unit44, KlingonLnxUnit200739, GIFImage, GraphicsConversionsLibrary,
MagnifierB200746, EmailUnit48, NoMoreImagesMsgUnit49, NoPixUnit50,
AVIresForm2007Unit45, ErrorLogUnit51;

[Tman]

"At last" added the solar elevation and azimuth (north=0°) for the current sol time and the decoded file name code.

[Tman]

Call me crazy, but it looks like I've made it to calculate equal LTST outputs from the filename code in comparison to the official (from sol 1420 up so far - probably for good). The clocks seem to be failing about a second per sol now - Oppy less than Spirit. But it would be great to get at any one time a tip when they have to do another larger leap.