Active Query Builder support area

When using CustomExpressionBuilder add a property that make the expression/criteria columns read only

Andrew Kennard

9 years ago
updated 8 years ago
Completed

Arrrggh :) This doesn't quite work but I though I would post it anyway as it might provoke a thought

In conjunction with my other two requests about editing SQL output columns with QT and exposing a cell reference in CustomExpressionBuilder so you know exactly which cell the ellipsis was clicked on.

Both of these requests could be 'avoided' if when using the CustomExpressionBuilder the Expression, Criteria and Or cells were all made 'read-only'

By that I mean you can click the ellipsis to launch a custom dialog to do what you like in, even provide a free type text box if one wishes but when the text is returned to the cell, if it is read only, You then know when the user next clicks on the ellipsis the OldExpression value will be as you set it i.e. they can't change it, the custom dialog is in total control

It doesn't get around one really needs to store some metadata to save having to 'reverse engineer' the OldExpression string to populate the custom dialog ..... but at least you would be in control of what you were reverse engineering

Thanks for listening !

Replies 39

Newest first
Newest first Oldest first

8 years ago

Thanks very much for this. As there are several parts to the request above please could you give me a few words about which changes you are making

Reply Link

Andrey Zavyalov, PM

Hello Andrew,

Sorry for keep you waiting for so long.

The new minor version will be ready next week. This improvement will be included in this release. We will notify you about this release.

Any news on this guys ?

Thanks

9 years ago

Thanks very much. I look forward resuming the conversation in May

I think we'll be able to implement this feature in May.

Hi, I hope your .NET version is going well.

Do you now have a better idea on when you might be able to get back to this for us ?

That's OK

I only put a couple of weeks tin o give you something to respond to

I am building something using your component to go in the next version of our product.

We have an internal Directors meeting here on the 11th of March so we can show where we are at and what specifications we need for the next stage

It would be good to be able to show your component off then in the best light but I will write something in the meantime to reverse engineer the OldExpression so I should be able to get it to a proof of concept stage by that meeting with the component as is

Good luck with your .NET version !

I'm afraid that this may happen not earlier than in 2-3 months, may be later. We have huge amount of work these days.

Thanks VERY much for this

Yes any time in the next couple of weeks would be brilliant

Whilst making them read-only gets around almost all of the challenges in that the user can't change the criteria outside of the custom dialog .....

Should the developer choose to offer a free type box then I believe they would need some way of knowing (via a flag they could set) that would tell them this was 'free typed' and therefore should just be placed back in that free type box in their dialog. Any code the developer has designed to "reverse engineer" the OldExpression value to populate their dialogs combo forms, check boxes etc could not be used due to the fact OldExpression could contain 'anything'

Hello,

I agree that disabling direct editing in Expression and Criteria/Or columns is a better way to solve your problem. Unfortunately we can not implement this feature right now. We'll get back to this as soon as we finish our job of releasing the final version of AQB.NET 3.0.