Can we use CC or PD logos?
https://commons.wikimedia.org/wiki/File:Twitter_icon.png
Public domain https://commons.wikimedia.org/wiki/Category:Facebook#/media/File:F_icon.svg

What are the kde/debian rules for such things?

Just to confirm the existence of the completer doesnt prevent manual entry?

eg, field datasource can contain =<Complex js > or $<literal string>

Not all item types allow 'extra value' to be specified for the data source. Are you happy allowing the property for all item types?

Is it possible to add some tests for the query strings that would be impacted by this?

• addres comments

Got following crash, when renaming the same field twice

• Re-order and andd envelope sizes

I cant reproduce this, is it fixed for you?

You are happy with 5.x?

could you confirm if 5.3.1 -> 5.3.4 are possible?

• Calculate sensible maximums for margin sizes

What do you think is a sensible max for margins? a % of the width/height? or some complex calculation involving calculating the size of the page and opposite margin?

In D5441#157528, @staniek wrote:

6. If 0.00 value is entered it disappears in the prop. editor when moving focus to another editor. Data is saved though. Expected: 0.00 is visible. Example for margins:
   
   
   
   
   
   This may or not be related to the KProperty libs and as such can belong to me :)

In D5441#157528, @staniek wrote:

6. If 0.00 value is entered it disappears in the prop. editor when moving focus to another editor. Data is saved though. Expected: 0.00 is visible. Example for margins:
   
   
   
   
   
   This may or not be related to the KProperty libs and as such can belong to me :)

Note, I cannot reproduce 7.3. Scrolling mouse over grididivsions works as expected.

• Set min/max values for grid divisions

• Fix dynamic redraw of background. Resolved issue 4.1 and 5.1

these issues explain the call to slotResizeBarDragged(0) ... need to find a fix wthout introducing it ... calling update() doesnt cause a resize to happen

• Fix section changing height when untis changed

• Fix custom page size handling when changing units

Fixes 2.2

fixed 2.1 and 2.3

• Fix items dissapearing

• Convert margins correctly when calculating page width

• Fix crash when changing unit of a line

• When changing section unit, set the unit before setting the height to

• Fixup margins to get basic rendering working again

rebased

• Minor fixes

• Move sections to d ptr

• Address comments

Ok, and for KReportDocument, move the protected m_ variables to d, and add protected getters/setters?

I thought for KReportASyncItemBase, we agreed because it was trivial, a dptr wasnt required. Thoughts?

• Is this the correct behaviour?

• Add size to printed page
• Get custom size to work in kreportexample
• Address comments
• Remove unused code
• Fix class enum

In D1263#134914, @staniek wrote:

When changing page CustomPageSize->Width property in the KReportExample's property editor, it is interpreted as Height. And coversely, Height is interpreted as Width.

{F3858801}

• Remove unused code

Just one question, what is the context where the connection related to a query schema is dynamic?

Better late than never :D

• Add KexiScriptingWarning

I have no such crash (3.1)

• Only filter out JS category messages, send others to stderr

• Enable the kexiadaptor object
• Enable KexiScriptAdaptor in the design view
• Start porting the kexidb module
• If it builds, relese it!
• Plug together the kdb wrappers
• Address comments
• Address comments
• Add KexiScriptingDebug
• No need to have an adaptor instance if they can be created at runtime
• Move execute from the view to the part
• Address comments
• Initialise
• Address comments
• Fixes
• Add stdout redirection to print JS output in the script designer

• Add size to printed page
• Get custom size to work in kreportexample
• Address comments

What is best, if you are happy with the engine port, do we push and work on the API separately? Do you want API changes for 3.1 or 4?