Re: [QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
Hi Ale,
That would explain it ;-)
I also tried various other combinations, like
with @current_parent_feature, @feature, etc. - but haven't found a
working version ...
I might try with a variable ;-) I got the variable filter version
working in another project. But that involved Python ...
Andreas
On 2022-12-06 16:52, Alessandro Pasotti wrote:
Sorry, I just realized that you are using relation-reference widgets
and not value-relation widgets.
I don't think that the current_(parent)_value will work in that case,
it wasn't implemented.
Cheers
On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
wrote:
Hi,
In one of my form setups, I would like to filter one relation
reference widget combo box with a filter expression based on the
selected entry of another relation reference value.
A static filter like:
szenario_art = 'Brand'
works as expected and it returns the filtered values - but as soon as
I try to base it on the value of another relation reference widget, it
fails ...
I tried
szenario_art = current_value('szenario_art')
but no records get selected.
Questions:
Does the current_value() return the "internal value" or the "human
readable" value?
Do I have to eval() something in the filter expression?
Is there a way to test "current_value" somehow? I tried to write the
changed value into another text widget (with default values on
update), but it will always return "NULL". In the expression editor, I
also always get "NULL" in the preview.
Thank you for your help,
Andreas
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-psc] QGIS budget 2023 RFC
Dear all, thanks a lot for all the feedback, As you might remember, the aim of the thread was indeed to discuss the proposed budget, so I'll to try to address most of the mentioned points in all emails without a specific order, trying to convey how things came to this proposal and why the PSC believes it is the best way forward for QGIS.org. As a first reminder, all the discussions happened in public, and you can read the minutes at https://github.com/qgis/QGIS/wiki#psc-meetings. The proposal came out of a need to solve a pressing issue we've been dragging along for some time now and "escalated" when Harrisou sent once again an appeal for help, and nobody from the developer ml responded [1]: I'll quote it as a reminder of the stark message showing how alone he felt in his efforts: >It's reassuring to discover that there are other channels; at >least I can say to myself that the total silence to my call is not due to >some disinterest. - Harrisou Even to this, the only answers were from Tim suggesting to Harrisou to join the next PSC to find solutions. The result of the PSC discussions was the proposal to add a full-time paid documentation person to effectively help Harrisou do what he has been trying to do for years alone. He is doing a tremendous job in a part of the project where it is challenging to get resources committed to it, and even when there were funds available, funded documentation efforts thus far have barely scratched the surface of the work that needs to be done. Even to the appeal above, the only answers were from Tim suggesting to Harrisou to join the next PSC to find solutions. Harrisou and Tim (Harrissou looking after docs, Tim looking after various web servers & sites) stand, as volunteers, to amplify their efforts through the paid helpers rather than have their efforts replaced by paid people. Regarding the QGIS infrastructure, the fact is that despite trying to onboard other people as volunteers, nobody is that interested in working on these things. Tim mentioned personally having walked various people through 'onboarding' as a sysadmin, and nothing came of it. Richard and Jürgen (who also help manage the infrastructure) may have different feelings, but Tim feels he is (allow me a direct quote here with his permission) "getting older and dumber," and we should have a plan in place to make sure the infrastructure that keeps the project running is professionally managed even when he will be too busy running his ever-growing farm :) Jürgen also mentioned the same issue regarding the infrastructure behind windows packaging in the past. Regarding transparency of the decision proposed, I'd like to separate the issue into three parts; 1) transparency regarding using Kartoza as a proxy, 2) transparency in hiring and finally and 3) transparency in the process of deciding to try hiring ‘outside’ people to support our project. Starting with the last point, I'd like to remind you all that we are indeed discussing if we want to accept this proposal right here in this thread, and finally, it will go to the voting members for decision-making. I really need help seeing how the PSC is not being transparent here. I'm saddened to see a perception of us trying to hide things when all is openly discussed/logged in reality. Regarding using Kartoza as a proxy company, it was indeed not selected based on being an open call - much like we appoint trusted developers to do bug fixing or other key efforts for the project. We are thankful to Kartoza for taking over the burden of doing it. Quoting Tim again: "It is only a hassle for us, and I only offered to do it through Kartoza to ‘make it happen’ rather than some desire to do it through Kartoza". Obviously, if the community wishes to use another company/individuals here, it is absolutely no problem to open the proxy up to another company. If anyone is interested, please contact the PSC mailing list with a concrete proposal on how to go forward. Finally, on the transparency in hiring: this doesn't make any sense to me. Hiring is a private process. People send their private CVs, often in secret, from their current employers, to whom they are being "disloyal". People applying should not have visibility of their competitors for the job. In the case of Kartoza, they have a POPIA [2] (something like GDPR), which governs what personal information they can share. Tim has shared all of the documentation writer's CVs with Harrissou, and he can pick whoever he thinks is best for the job. Tim also gave some recommendations based on basic screening of GIS skills, technical writing skills, whether they submitted a writing sample etc. For the infrastructure developer position, they sent all the applicants a standard assignment as they do as part of their normal recruitment process and had their developers review and shortlist. I don't know how we could sensibly (stressing that part since QGIS.org is not Google and the like...) do anything differently.
Re: [QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
Sorry, I just realized that you are using relation-reference widgets
and not value-relation widgets.
I don't think that the current_(parent)_value will work in that case,
it wasn't implemented.
Cheers
On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
wrote:
>
> Hi,
>
> In one of my form setups, I would like to filter one relation reference
> widget combo box with a filter expression based on the selected entry of
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable"
> value?
> Do I have to eval() something in the filter expression?
> Is there a way to test "current_value" somehow? I tried to write the changed
> value into another text widget (with default values on update), but it will
> always return "NULL". In the expression editor, I also always get "NULL" in
> the preview.
>
> Thank you for your help,
>
> Andreas
>
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Alessandro Pasotti
QCooperative: www.qcooperative.net
ItOpen: www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
You probably need to use current_parent_value() to get the value of
the "parent" form in case of embedded sub-forms.
On Tue, Dec 6, 2022 at 4:34 PM Andreas Neumann wrote:
>
> Hi Ale,
>
> Thanks for your information.
>
> What if both tables have the same column names? Would that also work?
>
> In my case the related table contains a field called "szenario_art" and the
> parent table also has the same field name.
>
> Can one assume that a field left of the operator will be in the related table
> while fields right of the operator are in the parent table? Or how would the
> expression distinguish the fields if they appear in both tables?
>
> Thanks,
> Andreas
>
> On 2022-12-06 16:29, Alessandro Pasotti wrote:
>
> On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
> wrote:
>
>
> Hi,
>
> In one of my form setups, I would like to filter one relation reference
> widget combo box with a filter expression based on the selected entry of
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable"
> value?
>
>
> The internal value.
>
> Do I have to eval() something in the filter expression?
>
>
> No.
>
> Is there a way to test "current_value" somehow? I tried to write the changed
> value into another text widget (with default values on update), but it will
> always return "NULL". In the expression editor, I also always get "NULL" in
> the preview.
>
>
> That should work, the current_value returns the current value of the
> feature being edited in the context of the form, this includes any
> change that took place in the form.
>
> You might get null values in the editor and the preview because there
> is no form context in that case.
>
>
>
>
--
Alessandro Pasotti
QCooperative: www.qcooperative.net
ItOpen: www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
Hi Ale,
Thanks for your information.
What if both tables have the same column names? Would that also work?
In my case the related table contains a field called "szenario_art" and
the parent table also has the same field name.
Can one assume that a field left of the operator will be in the related
table while fields right of the operator are in the parent table? Or how
would the expression distinguish the fields if they appear in both
tables?
Thanks,
Andreas
On 2022-12-06 16:29, Alessandro Pasotti wrote:
On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
wrote:
Hi,
In one of my form setups, I would like to filter one relation
reference widget combo box with a filter expression based on the
selected entry of another relation reference value.
A static filter like:
szenario_art = 'Brand'
works as expected and it returns the filtered values - but as soon as
I try to base it on the value of another relation reference widget, it
fails ...
I tried
szenario_art = current_value('szenario_art')
but no records get selected.
Questions:
Does the current_value() return the "internal value" or the "human
readable" value?
The internal value.
Do I have to eval() something in the filter expression?
No.
Is there a way to test "current_value" somehow? I tried to write the
changed value into another text widget (with default values on
update), but it will always return "NULL". In the expression editor, I
also always get "NULL" in the preview.
That should work, the current_value returns the current value of the
feature being edited in the context of the form, this includes any
change that took place in the form.
You might get null values in the editor and the preview because there
is no form context in that case.___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
On Tue, Dec 6, 2022 at 3:59 PM Andreas Neumann via QGIS-Developer
wrote:
>
> Hi,
>
> In one of my form setups, I would like to filter one relation reference
> widget combo box with a filter expression based on the selected entry of
> another relation reference value.
>
> A static filter like:
>
> szenario_art = 'Brand'
>
> works as expected and it returns the filtered values - but as soon as I try
> to base it on the value of another relation reference widget, it fails ...
>
> I tried
>
> szenario_art = current_value('szenario_art')
>
> but no records get selected.
>
>
> Questions:
>
> Does the current_value() return the "internal value" or the "human readable"
> value?
The internal value.
> Do I have to eval() something in the filter expression?
No.
> Is there a way to test "current_value" somehow? I tried to write the changed
> value into another text widget (with default values on update), but it will
> always return "NULL". In the expression editor, I also always get "NULL" in
> the preview.
That should work, the current_value returns the current value of the
feature being edited in the context of the form, this includes any
change that took place in the form.
You might get null values in the editor and the preview because there
is no form context in that case.
--
Alessandro Pasotti
QCooperative: www.qcooperative.net
ItOpen: www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Question on current_value() expression in the context of filtering relation reference combo boxes
Hi,
In one of my form setups, I would like to filter one relation reference
widget combo box with a filter expression based on the selected entry of
another relation reference value.
A static filter like:
szenario_art = 'Brand'
works as expected and it returns the filtered values - but as soon as I
try to base it on the value of another relation reference widget, it
fails ...
I tried
szenario_art = current_value('szenario_art')
but no records get selected.
Questions:
* Does the current_value() return the "internal value" or the "human
readable" value?
* Do I have to eval() something in the filter expression?
* Is there a way to test "current_value" somehow? I tried to write the
changed value into another text widget (with default values on update),
but it will always return "NULL". In the expression editor, I also
always get "NULL" in the preview.
Thank you for your help,
Andreas___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
