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

Adding textChanged notification to SpStringTableColumn #1360

Merged
merged 7 commits into from
Apr 12, 2024

Conversation

colorow
Copy link
Contributor

@colorow colorow commented Mar 4, 2023

This is a fix for issue #12884 on Pharo-project-pharo

Currently an SpStringTableColumn can be set to editable, but the changes are only sent to the table #items when the user does a carriage return.

This change adds a text changes event which will sent updates to the table at each keystroke.

I could not figure out a way to write a test case for this, as the editing occurs in a popup text input over the string column. But I did include a change to SpTablePresenter >> exampleWriteableTable which excercises the change. To run this code:

  1. Open a Transcript.
  2. Execute "SpTablePresenter exampleWriteableTable" in a Playground.
  3. Edit and cell in the left hand column. Changes should show in the Transcript.

colorow added 6 commits March 4, 2023 14:33
…along with the current carrige return acceptance.

I couldn't find a way to create a unit tes for this as the edits take place in a popup string input morph and there are no easy controls of that from the String colum or the table presenter.  However, I did update SpTablePresenter??exampleWriteabltTable to test this.  
In order to test: 
1.  Open a Transcript window.
2. execute SpTablePresenter exampleWriteableTable in a Playground.
3.  Click your mouse into any row of the left hand editable column and edit a field.  Updates should be written to the Transcript.
@jordanmontt
Copy link
Contributor

Hello, what is needed to accept this PR? @estebanlm

@estebanlm estebanlm closed this Oct 20, 2023
@estebanlm estebanlm reopened this Oct 20, 2023
@estebanlm estebanlm changed the base branch from Pharo11 to Pharo12 October 20, 2023 07:16
@estebanlm
Copy link
Member

@jordanmontt first of all this should now be going to Pharo12 branch, not to Pharo11 ;)

@jordanmontt
Copy link
Contributor

It seems that you changed the target branch :)

@estebanlm estebanlm closed this Apr 12, 2024
@estebanlm estebanlm reopened this Apr 12, 2024
@estebanlm
Copy link
Member

lol, this thing never went to the trunk :P
checking now if we can add it.

@estebanlm estebanlm merged commit 6909e9e into pharo-spec:Pharo12 Apr 12, 2024
2 of 4 checks passed
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.

3 participants