Forum

Notifications
Clear all

Quartex Pascal Build 0.17.2

3 Posts
2 Users
1 Reactions
517 Views
Jon Lennart Aasenden
(@tao4all)
Posts: 44
Member Admin
Topic starter
 

Finally! This build contains quite a bit of fixes that had been lurking around the RTL and IDE for some time, so we are getting close to the RC1 (release candidate)!

May be an image of screen

Fixes and additions

  • Rolled back to previous DWScript which is stable
  • Fixed a problem with TQTXDynamicApplication model where the ShowForm() failed due to mistaken reintroduction
  • Fixed a problem with TQTXBoxedApplication model where a similar reintroduce caused issue. Both of these further affected the "ShowForm" method, so it was very fortunate that we fixed these now
  • The codegen omitted width when emitting code for TQTXBoxedApplication forms, which it should -- this has now been fixed
  • Gave all widgets in the RTL icons. The default green puzzle piece is now reserved for clean HTML definition components (e.g 1:1 wrappers over direct HTML tags, like <Table> or <option> style elements). It also remains as a default glyph in case someone register a widget without a glyph
  • All widgets have been given a [DefaultName('<name here>')] attribute, so that when you add a widget it is not named "widget1" or "Widget2" but rather "button1" or "listbox1" -- which is what you expect and have in both Delphi and Lazarus.
  • Added a clean TQTXLeafletMap example, which demonstrates RT's leaflet map package. Also gave that widget a google maps glyph (not sure it actually uses Google maps, that that is easy to fix).
  • Fixed a problem where WWR (web worker units) was not properly parsed and thus had no unit overview
  • Went over the code that resolves unit-file names, so it's faster and more maintainable
  • .. and much, much more!

Download

Visit our Patreon website to download the binaries

This topic was modified 2 years ago by Jon Lennart Aasenden
 
Posted : 12/02/2023 7:14 pm
RTOlivier reacted
(@rtolivier)
Posts: 6
Active Member
 

? Thank you for this build.

Is it possible to add Default Delegate(Handler) with the next build too? What I mean is: When the user Double-Click on a widget on then Designer. It add automatically the default Delegate(Handler) and brings to the editor (Like in Delphi or Lazarus).

Easy implementation of this may be:

//TQTXMetroUISplitButton
  [RegisterInfo('MetroUI Split Button Component')]
  [RegisterWidget(pidBrowser, ccContainers)]
  [BindDelegates([
    TQTXDOMMouseClickDelegate,
    TQTXMetroUISplitButtonClickDelegate
  ])]
[RegisterDefaultDelegate(TQTXDOMMouseClickDelegate)]

The custom Attribute: RegisterDefaultDelegate will register TQTXDOMMouseClickDelegate delegate as the default one. It will override allready registerred default delegate of ancestor widget.

Thank you,

Toky Olivier R.

 

 
Posted : 19/02/2023 3:11 am
Jon Lennart Aasenden
(@tao4all)
Posts: 44
Member Admin
Topic starter
 

When you double click a widget that is a container, the plan is that a new designer comes up so you can add widgets to it (work in progress!). This is where i wanted to place custom editors that you can script (dwscript). So I have some plans for that event 🙂

 
Posted : 21/02/2023 11:06 am
Share: