Add sg.Text as available field element / Add edit-protecting a button #138
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Only needed 1 change. I updated the update_event_states to be type(element) in to match.
Added ability to map_element a column-less element. Allows edit-protecting any button using a key-name, and very little code. I think it's pretty slick. But what do you think?
ssweber
changed the title
|
Sorry, I had to add the Edit-protect a sg.CalendarButton to the other fix, because it had merge-conflicts. If you don't like the sg.CalendarButton, I can repull just the sg.Text one. |
|
Don't merge this yet, somehow it screws up the Quick Editor... looking into it |
|
k, its working now, and I made sure wouldn't have issues elsewhere |
|
I actually think it's better off done on the users end anyway. Really all
that needs done is to set the elements state to not frm.edit_protect in the
main loop of the users application to edit protect anything. Perhaps an
example would be more appropriate. Or a helper function in pysimplesql:
def edit_protect_element(self):
return not self.edit_protect
Then the user can just use it in an element update on the main loop to
enable)disable the element
…On Wed, Mar 8, 2023, 3:46 PM ssweber ***@***.***> wrote:
Don't merge this yet, somehow it screws up the Quick Editor... looking
into it
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQX2REWSSROCFGT2FA753BDW3DV23ANCNFSM6AAAAAAVUARNGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Ok, I'll close and repull just the sg.Text. I'm too much of a noob to figure out how to do it in the main-loop! Do you need to use a timeout? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only needed 1 change.
For update_element_states:
Didn't add to update_event_states, because you can't disable text.
Didn't know about adding it to visible=visible section.
I updated the update_event_states to be type(element) in to match.