Guys,
Anybody else interested in getting F1 to show the offline help if context-sensitive help is not appropriate?
I've gotten partway there but need some help:
http://bugs.freepascal.org/view.php?id=23411
Thanks a lot,
Reinier

Mailing lists / lazarus / 2013-03
9 messages · 2 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Guys,
Anybody else interested in getting F1 to show the offline help if context-sensitive help is not appropriate?
I've gotten partway there but need some help:
http://bugs.freepascal.org/view.php?id=23411
Thanks a lot,
Reinier
Reinier Olislagers wroteGuys, Anybody else interested in getting F1 to show the offline help if context-sensitive help is not appropriate?
i followed a wiki page that the help points to... the only thing i'm not sure of is why it doesn't get built automatically when i update from SVN and build... i'll be working on something and then hit the F1 key and realize that the help stuff is being built... weird...
I've gotten partway there but need some help: http://bugs.freepascal.org/view.php?id=23411
or... maybe i've misunderstood your goal above?
The only thing that is built once is the lhelp executable. Having lhelp built when doing a make all or a lazbuild bigide would make sense IMO, yes, but is different from the issue I linked to.
<ad>
fpcup builds it for you ;)...
</ad>
... but if you're using shell/batch scripts it's easy enough to do so, too.
> I've gotten partway there but need some help: > http://bugs.freepascal.org/view.php?id=23411 or... maybe i've misunderstood your goal above?
I think so, yes. I'm interested in getting a menu item that shows Help (not just Online Help) and having an F1 press result in getting lhelp with the table of contents/index/whatever up so a user can peruse the help - unless he's pressing F1 on an identifier, in which the current context-sensitive help can pop up as usual.
Anybody else interested in getting F1 to show the offline help if context-sensitive help…
Thanks Mattias for your post on the bugtracker issue... I'll look into it!
i followed a wiki page that the help points to... the only thing i'm not sure of is why…
Just had a quick look through the Lazarus makefile.fpc - seems lhelp gets built as part of a bigide build. So just make sure you do a bigide build after your SVN checkout...
that's too much... my script already does the following specifically to not use bigide...
:setvals
set task1=before svn update...
set step1=make clean
set task2=updating lazarus from svn...
set step2=TortoiseProc /command:update /path:"%myLAZpath%" set task3=build lazbuild, startlazarus and necessary tools... set step3=make lazbuild lcl ideintf basecomponents starter set task4=save existing lazarus.exe...
set step4=if exist lazarus.exe copy /y lazarus.exe lazarus.save.exe set task5=Clean Up + Build all
set step5=rem lazbuild.exe --build-ide= --build-mode="clean up + build all" set copy5=rem copy lazarus.exe lazarus-clean_up_build_all.exe set task6=Normal IDE
set step6=rem lazbuild.exe --build-ide= --build-mode="normal ide" set copy6=rem copy lazarus.exe lazarus-normal.exe
set task7=Debug IDE
set step7=lazbuild.exe --build-ide= --build-mode="debug ide" set copy7=rem copy lazarus.exe lazarus-debug.exe
set task8=Optimized IDE
set step8=rem lazbuild.exe --build-ide= --build-mode="optimized ide" set copy8=rem copy lazarus.exe lazarus-optimized.exe set task9=Copy chosen IDE to lazarus.exe
set step9=rem copy lazarus-debug.exe lazarus.exe
i guess maybe i should add lhelp to step3? the question is in what position in the given line...
NOTE: steps 5, 6, 8 and 9 are REM'd out in the command passed to the function... so we're only generating the debug ide and using that for all work...
sorry, my crystal ball is in the shop for polishing ;)
wild guess: at the end!?
have not had coffee yet... forgot - if you actually use the make command i don't think it will matter much...
sorry, my crystal ball is in the shop for polishing ;) wild guess: at the end!?
polishing? if only we were so lucky... our's always have to go back after one good result because they fail on the next attempt... the shop can't find the problem... evidently their crystal balls don't work as desired either ;)
i've thought about that... the above order came from the original make file and a little playing... since everything is saved in the compilation log file... but wading thru that can be a real chore :?
i've still a few more messages to read... i'm hoping that a definitive answer will be given so i don't have to dance such a long dance between tests... this machine isn't the fastest thing around... c0ffee and a few smokes is on the agenda once a SVN update and compile cycle is started...