Farshad Mohajeri

http://forums.unigui.com/index.php?/topic/2100-sebaot-web/page__view__findpost__p__9340

It is by design and not a bug. There should be no problem for any particular app if there is one or if there are N number of scroll events. I recommend you to redesign your app so it can cope with N number of scrolls. You shouldn't take default VCL behavior as reference when designing your web app.

You must use MonitoredKeys property of parent Form.

Not directly from Delphi, but you may try playing with config params of Ext.Panel in UniPanel.

Logged #1359

Search in google or Embarcadero forums about how to reduce exe size.

What is your Delphi version? XE2 can produce big exe files. There are ways to reduce it but in general it causes no problem because DLL is loaded into memory only once.

You need to give more details on this.

Are you using code from this example? http://forums.unigui.com/index.php?/topic/1741-formatted-input-for-uniedit/page__view__findpost__p__7294 If yes, delpoy same files as done in the demo in above link.

So did you copy those extra JS files to your server?

In 0.89 use can use: var frm = MainForm.UniURLFrame1.iframe;

Application.ProcessMessages is a VCL thingy and has no affect on how Web mode works. Actually it can crash your app and its usage is discouraged.

This code has nothing to do with standard unigui output. What type of app is this?

I'm not sure about the exact parameter. Must be somewhere in Pool settings: Allow 32-bit apps

Our instructions are for 32-Bit version of 2003 server. In a 64-bit server there is an extra settings to allow 32-bit apps run in application pool. Check your Pool settings for this detail.

Main problem with Delphi 7 is Frames. There is no way to implement and install a custom TFrame descendant in Delphi 7.IDE:

I can't reproduce in Chrome. Send a test case please.

Probably because you don't have a component named: UniURLFrame1

unigui only creates MainForm at start. Other forms are created on demand. In a DB app generally there is one DB connection which is shared among other Forms in app. That's the main reason of putting DB connection on MainModule. Also it speed ups your app because there is no need to establish a new connection each time you create a Form instance. There is no restriction on where you can place DB components. It is only a matter of design. However, in future we may develop pool for dataModules to save resources. In this case putting db components on dataModule will make a difference. Changing port with change your caller URL. http://myserver:8090/myapp/my.dll

Have you compiled your app for ISAPI mode and get the dll output? Please start from scratch with a new app containing a blank form only and briefly describe all steps you took.

What does your complete code look like?

Have you read our docs regarding this? http://www.unigui.com/doc/online_help/index.html?iis_6_0.htm

You can't create a Form dynamically and then refer to its "static" instance. Creating a dynamic form doesn't initialize its reference as we define as: function DynamicForm: TDynamicForm; Calling DynamicForm() inside a dynamically created form will create a 2nd instance. Corrected: Metka : begin pComponent := Self.CreateTUniLabel; pComponent.Tag := 1; end;

Yes, but Delphi has its roots in Windows. Current version of uniGUI is dependent to VCL and WinAPI and not portable to Linux/FPC. Not sure what will happen in future. It all depends on market demand.

Internal class structure is being prepared in a help system similar to Delphi. You can see ClientInfo demo for your question.