Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix editable attribute of joined fields (fix #7739) #576

Closed
wants to merge 2 commits into from

Conversation

minorua
Copy link
Contributor

@minorua minorua commented May 5, 2013

@ghost ghost assigned wonder-sk May 7, 2013
@gioman
Copy link
Contributor

gioman commented Jun 16, 2013

Hi, can this patch be committed so I can test it and then eventually close the ticket? Thanks!

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

It works, but it's still easy to turn the field to an editable one in the layer properties. Is this intended behavior?

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

Sidenote: Would it not be easier to just set the editable state in QgsAttributeEditor::createAttributeEditor?

@minorua
Copy link
Contributor Author

minorua commented Jul 3, 2013

It works, but it's still easy to turn the field to an editable one in the layer properties. Is this intended behavior?

No. It would be better to disable/hide Edit-widget-button/editable-checkbox of joined fields in the layer properties dialog.

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

PS:
Just check for the FieldOrigin in QgsVectorLayer::fieldEditable() would probably be even cleaner. (But the buttons still need to be adjusted)

@m-kuhn m-kuhn closed this Jul 3, 2013
@m-kuhn m-kuhn reopened this Jul 3, 2013
@minorua
Copy link
Contributor Author

minorua commented Jul 3, 2013

updated the commit and add a commit to disable edit type buttons of joined fields (the previous one is minorua@7f0bbf4).

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

Did you disable the whole widget config dialog? Should not only the editable button be disabled?

And what do you think about simply checking the FieldOrigin in fieldEditable() ?

@minorua
Copy link
Contributor Author

minorua commented Jul 3, 2013

Those were enough for me. Any improvement about this patch is welcome. :)

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

Sorry, I did not want to steal your time :-)
But do you agree to the remarks I made?

@minorua
Copy link
Contributor Author

minorua commented Jul 3, 2013

But do you agree to the remarks I made?

@Matthias-Kuhn You know better than I do. I'll cooperate with the test if you modify something about this issue.

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

I wasn't sure if I overlooked something, these were just ideas. I'll try to come up with a patch...

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

@minorua would you be able to test the referenced pull request.

@minorua
Copy link
Contributor Author

minorua commented Jul 3, 2013

@Matthias-Kuhn Great! I've just tested your branch. All (attribute list in the properties, edit form and writing xml) works expectedly. Thanks!

@minorua minorua closed this Jul 3, 2013
@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2013

Merged. Thank you for your work and the testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants