v11.3.9 gives an error whenever I try to navigate it using the tab & arrow keys.

[casualfan]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Platform

[e.g. Windows 10, Windows 11, Mac, Linux (State distribution)]

Log Files
Attach your Libation log file here.
The owning DataGridViewCell object has not been set.

at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_ParentPrivate()
at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_Bounds()
at System.Windows.Forms.DataGridViewCell.System.Windows.Forms.IKeyboardToolTip.GetNeighboringToolsRectangles()
at System.Windows.Forms.ToolTip.GetOptimalToolTipPosition(IKeyboardToolTip tool, Rectangle toolRectangle, Int32 width, Int32 height)
at System.Windows.Forms.ToolTip.ShowKeyboardToolTip(String text, IKeyboardToolTip tool, Int32 duration)
at System.Windows.Forms.KeyboardToolTipStateMachine.ShowToolTip(IKeyboardToolTip tool, ToolTip toolTip)
at System.Windows.Forms.KeyboardToolTipStateMachine.Transition(IKeyboardToolTip tool, ToolTip tooltip, SmEvent event)
at System.Windows.Forms.KeyboardToolTipStateMachine.Transit(SmEvent event, IKeyboardToolTip source)
at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lparam)

[rmcrackan]

Thanks for the bug report. This looks related to a piece of code I touched recently so I assume I created a bug. I'm not able to make this happen on my computer though. Can you attach your latest log file? You can find it here: Libation > Settings > click "Open log folder"

[casualfan]

is it a zip file?

[rmcrackan]

Yes

[casualfan]

_Log202405.zip

[rmcrackan]

This is disturbing. I can't make it happen for me no matter what I do but I see in your logs that it happened to you 3 times within a few seconds. Has it happened again since then?

[CLHatch]

This is disturbing. I can't make it happen for me no matter what I do but I see in your logs that it happened to you 3 times within a few seconds. Has it happened again since then?

Perhaps something to do with the version of Windows being used? I'm using Windows 11 here. If by any chance he's on Windows 11 and you on Windows 10, might not show up on your end?

[CLHatch]

I just switched from 11.3.9 Chardonnay to 11.3.9 Classic, hit the tab key a few times, and got an error myself.

The owning DataGridViewCell object has not been set.

   at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_ParentPrivate()
   at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_Bounds()
   at System.Windows.Forms.ToolTip.ShowKeyboardToolTip(String text, IKeyboardToolTip tool, Int32 duration)
   at System.Windows.Forms.KeyboardToolTipStateMachine.ShowToolTip(IKeyboardToolTip tool, ToolTip toolTip)
   at System.Windows.Forms.KeyboardToolTipStateMachine.Transition(IKeyboardToolTip tool, ToolTip tooltip, SmEvent event)
   at System.Windows.Forms.KeyboardToolTipStateMachine.Transit(SmEvent event, IKeyboardToolTip source)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lparam)

[CLHatch]

OK, deleted the log files and started up again, started tabbing, and the error pops up as soon as I tab to the first "stoplight".

The owning DataGridViewCell object has not been set.

   at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_ParentPrivate()
   at System.Windows.Forms.DataGridViewCell.DataGridViewCellAccessibleObject.get_Bounds()
   at System.Windows.Forms.ToolTip.ShowKeyboardToolTip(String text, IKeyboardToolTip tool, Int32 duration)
   at System.Windows.Forms.KeyboardToolTipStateMachine.ShowToolTip(IKeyboardToolTip tool, ToolTip toolTip)
   at System.Windows.Forms.KeyboardToolTipStateMachine.Transition(IKeyboardToolTip tool, ToolTip tooltip, SmEvent event)
   at System.Windows.Forms.KeyboardToolTipStateMachine.Transit(SmEvent event, IKeyboardToolTip source)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lparam)

_Log202405.zip

Edit:
Just to verify, I switched back to 11.3.9 Chardonnay, started tabbing, and no errors.

[rmcrackan]

Thanks. You both appear to have auto-scan enabled but I don't so I turned it on and restarted. I can now force this to happen if I use my arrow keys like crazy while the initial scan is happening. This is going to be a weird one...

[CLHatch]

Thanks. You both appear to have auto-scan enabled but I don't so I turned it on and restarted. I can now force this to happen if I use my arrow keys like crazy while the initial scan is happening. This is going to be a weird one...

If you mean the top setting here...

I did have that turned on. But i just now turned that off, and still getting the same error.

[CLHatch]

It also ONLY gives me an error when I tab to one of the "stoplights".

[CLHatch]

Recording.2024-05-13.132223.mp4

Here's a recording of it, right after starting Libation.

[rmcrackan]

Thank you so much for this. This is maddening. This error will happen only for the version which is built for the public. The way I run it for debugging, this error will not occur. So I can't reproduce it in a way that can be easily debugged. This is going to be a weird one.

[CLHatch]

Thank you so much for this. This is maddening. This error will happen only for the version which is built for the public. The way I run it for debugging, this error will not occur. So I can't reproduce it in a way that can be easily debugged. This is going to be a weird one.

Oh, fun. :-D

Well, at least you know where to look. I'm guessing something to do with the changes in the "stoplight" you did to make the text readers work in that field.

Edit:
UNLESS it's a bug that existed in previous releases that was never noticed. Do we know if this happened in previous releases or not?

[rmcrackan]

I'm guessing something to do with the changes in the "stoplight" you did to make the text readers work in that field.

Almost certainly. No good dead goes unpunished.

[CLHatch]

I'm guessing something to do with the changes in the "stoplight" you did to make the text readers work in that field.

Almost certainly. No good dead goes unpunished.

Just to be sure, I rolled back to Libation Classic 11.3.8, and no error on tabbing to the stoplights.

[rmcrackan]

Fixed in the latest version 11.3.11 -- https://github.com/rmcrackan/Libation/releases/tag/v11.3.11

(I know I skipped 11.3.10. The explanation is technical and utterly boring.)

Please let me know if it still gives you errors. Thank you both for your patience and help!!

[CLHatch]

Fixed in the latest version 11.3.11 -- https://github.com/rmcrackan/Libation/releases/tag/v11.3.11

(I know I skipped 11.3.10. The explanation is technical and utterly boring.)

Please let me know if it still gives you errors. Thank you both for your patience and help!!

I can verify that it fixed it on my end, and Chardonnay also still working.

[rmcrackan]

Thanks for checking but Chardonnay is actually untouched in these last few releases. This is Classic only.

I'd love to retrofit Chardonnay for screen readers but I just don't have it in me. I'm trying hard to keep Classic as accessible as possible though.

[CharlieRussel]

Working correctly here. (But I hadn't updated for the last several, so never actually had it hit me. And yes, I'm on Classic.)

[CLHatch]

Thanks for checking but Chardonnay is actually untouched in these last few releases. This is Classic only.

I'd love to retrofit Chardonnay for screen readers but I just don't have it in me. I'm trying hard to keep Classic as accessible as possible though.

Yeah, had a feeling it was untouched, but figured best to verify the changes in Classic didn't break Chardonnay, in case there was some shared code there. :)

[rmcrackan]

Good call. There's actually an enormous amount of shared code. This happens to be in the thin purely UI part, which is separate between the 2.