![]() ![]() VFI - Visual Form Inheritance Short Descriptionįorms can inherit from other forms. ![]() Propagate changes of ancestor to nested controls.Forbid putting a component onto a nested frame, because TWriter does not support that.show nested components in OI component tree.When Ctrl+Click on inherited nested components events in OI jump to inherited code.When dblclick on inherited nested components events in OI create an event with the following code: Frame1.FrameResize(Sender).Show inherited nested components events in OI as ClassName.MethodName.Forbid renaming nested inherited components.Forbid deleting nested inherited components.Show inherited nested components properties in OI.Inherited nested Components (Components with the frame as Owner and not the Form).Close a frame that is currently used by a nested frame.Add a frame to a form, add unit to uses section, package to project dependencies.Support for the inline keyword for lfm and lrs streams.Design a frame (adding, selecting, moving controls.The goal is to edit them like forms in the IDE designer, and to use them as components on designer forms.Ĭompile lazarus clean with passing -dEnableTFrame (not necessary starting from svn release 16909) standardize filenames and path, so that loading the translations at runtime is possible without writing code.įrames are special child forms.This directory can then be used by the project to load the strings at runtime. po files of project and all used packages into a directory. po file for each package (implemented, need dialog option to change po filename or need agreedment to use same name of package) Copying new strings from rst and lrt files to a single.po files, similar to the updatepofiles tool. Collect TTranslateStrings from RTTI while designer form writing and writing them to lrt file.Dialog options for project/package to enable i18n.This feature automatically creates and updates. Translations, i18n, lrt files, po files Short Description So the uses section is a good compromise between speed and flexibility. Without the uses section the IDE must in worst case search and read every reachable lfm file on disk. But the IDE must somehow find the referenced form. Technically there is no connection between the uses section and the form streaming, because form streaming uses global variables. Allow to connect to forms, that are used in the uses section.Reopen/Revert a form - all connected forms are now closed.Opening a unit now checks if designer is already created.When referenced component is deleted, the using units must be set modified.When referenced component is renamed, the using units must be set modified.When all referring forms are closed/hidden, the hidden component will be automatically freed.When target form is closed, then only the designer is closed.When reference form is opened, then target forms are opened too.But the designer must be flagged 'modified', because the lfm has changed. When a component is renamed the property does not need to be updated, because the form is open and use the pointer not the name.Maybe eventually a check could be added, if this is implemented properly and force a nil on error. When component is deleted, the property must be set to nil - This is not the job of the IDE, but should be achieved by the normal TComponent FreeNotification feature.TPersistentPropertyEditor.SetValue - search the component via the given path.TPersistentPropertyEditor.GetValue - Show component path.Check for class compatibility and if the target form is listed in the CreateForm statements of the lpr file and if the target unit does not belong to a package that will conflict if used. TPersistentPropertyEditor.GetValues - List all possible values. ![]() #FREE PASCAL IDES MANUAL#Manual referencing via source code works.A common example is to use the TDataSource on a DataModule for the DataSource property of a db control.ĭesigner forms can only reference each other if they have a CreateForm statement in the lpr file (Project Options / Forms). This feature allows to use components of other designer forms. Multi form properties / using DataModules from other forms in the designer Short Description 2 Translations, i18n, lrt files, po files.1 Multi form properties / using DataModules from other forms in the designer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |