Syntax: Syntax: GO|targetPageID|[optionalTags|]visiblePhrase||elsePhrase
Any changes made to the session data during exporting will be discarded. Yes, this is possible - you could use a SET macro to set flags and that would impact the literals. Ordinarily, those changes would be saved but that is explicitly turned OFF during exporting.
This also fixes the problem where you could not test with a 1exe Hub because "Delphi" was using up on of the slots in the Hub. For anyone using a prior version before the fix - set UseWebHub to false and Delphi will no longer show on the Connected panel.
If the INI file is connected and sections for the prior component name are detected, they will be renamed to the new component name (eg. ButtonSpecs) and if the component name was embedded in the syntax, the syntax will automatically be adjusted to use the new component name. Yes!
Fact: You can add event handlers to objects such as the TWebApp, for example, TWebApp.OnExecute.
Limitation prior to v1.491: You can only do that once. And if we do it, say in the shared appmain.pas form, then you can't do it without touching the official shared form and breaking "the standard".
Why this might come up: When the app object refreshes, various project-dependent things need to happen, such as refreshing the webmail panel, the webcycle component or the weblogin component. etc. etc. depending on the project.
Breakthrough: now you can make a LIST of event handlers for a single event, and all handlers in the list will be called. The core code for this is in a new unit, htEvtLst.pas, available with source to registered customers. An example of how this can be used is in the shared ht\htfrm\whMail.pas unit, where it is necessary to hook into the TWebApp.OnUpdate event handler.
This code is also used in the new shared ht\htfrm\dmExtens.pas unit.
The way this works is that the original event handler is replaced with a substitute event handler that calls the original one plus any number of additional handlers. While in practice this is unlikely to exceed 3 or 4 levels, there is no arbitrary limit on the number of handlers in the list.
New demos - you will find them all on demos.href.com:
Registered customers who are upgrading have the option of installing a set of files that includes the Hub and the VCL, without demos or docs.
self.classname
. You can rebuild
your packages using the totally nifty .bat file that you will find in ht\pkg.
Hub.exe v1.494 (only) does not run on 1 system - gives a flurry of errors on start. If anyone else sees this problem, please write to ann@href.com.
If you choose Help|Registration and click [Cancel] you will invalidate your Hub capacity. Do it again and click [Ok] to restore.
Hub UI freezes, sometimes. If anyone can reproduce this at will, please advise ann@href.com.
The webhub.hlp file has invalid links from the VCL components page to TWebCycle and TWebLogin. However those components are in the help file, just search for them by name.
Problem with nested macros not expanding - fixed in v1.495.