Follow-up to my previous patch; this fixes an issue where the mouse_leave
event was never sent because maybe_last_handler was only set when there
was already a maybe_last_handler widget set.

The change here makes it so that every time an event is consumed libvaxis
keeps track of which widget did that through the maybe_last_handler
variable.

In other words: we update maybe_last_handler every time an event is
explcitly consumed.
---
 src/vxfw/App.zig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
[message trimmed]

The MouseHandler used to only consume the mouse events if there was a
last_handler widget defined AND whoever is using the API set
ctx.consume_event to true.

This change makes it so the event is consumed when ctx.consume_event is
set to true, even if there is no last_handler widget defined.
---
 src/vxfw/App.zig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/vxfw/App.zig b/src/vxfw/App.zig
index 5b50fa0..b4408b7 100644
--- a/src/vxfw/App.zig
+++ b/src/vxfw/App.zig
[message trimmed]

The MouseHandler used to only consume the mouse events if there was a
last_handler widget defined AND whoever is using the API set
ctx.consume_event to true.

This change makes it so the event is consumed when ctx.consume_event is
set to true, even if there is no last_handler widget defined.
---
 src/vxfw/App.zig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/vxfw/App.zig b/src/vxfw/App.zig
index 5b50fa0..b4408b7 100644
--- a/src/vxfw/App.zig
+++ b/src/vxfw/App.zig
[message trimmed]

All unread messages are highlighted with a gray background. This is
currently the same color used on mouse hover, simply because it was easy
to copy.

A channel is marked read when:

* You switch channel (either via mouse or keyboard); or
* you send a message.

This means that new messages _from others in the channel_ will remain
unread until you either:

* send a message; or
* change the current channel.
[message trimmed]

Hi Brad! Would love to join the 1MB club if you'll have me :)

Arc DevTools say 185.4 kB transferred with caching disabled, but feel
free to update it with whatever value you see from Firefox.

Thanks!

-Kristófer R.

---
 _site_listings/thorlaksson.com.md | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 _site_listings/thorlaksson.com.md
[message trimmed]

Hi again Christian,

I've just published version 1.3.0 of Intelephense with support for 
adding a license key and using the premium features Nova supports. As 
far as I've been able to tell that's really just the "Jump to 
implementations" feature for now, but maybe there are other things I 
just don't know how to find in Nova's UI.

-- 

Best regards,
Kristófer R.

Hi Martin,

> it would be great if the Intelephense Nova extension would have a per project setting for enabling’/disabling the extension.

I've just added this in version 1.3.0 of the extension released tonight :)

-- 
Best regards,
Kristófer R.

Hi, I've just added this to the upcoming version 1.3.0 that will be 
released later tonight. All the diagnostics options should be available 
with that version.

Hope that helps!

-- 

Best regards,
Kristófer R.

Hi! Thank you for bringing this to my attention, and sorry for the late 
reply!

> It looks like I would need to set intelephense.diagnostics.undefinedProperties = true, but I don’t know how to do that with this extension.

This wasn't an option before. Intelephense has a lot of configurable 
options and I didn't add them all because it takes a lot of time. I've 
already implemented this and it will become available in the upcoming 
1.3.0 version of the plugin that should be published later today.

Let me know if you're still running into this problem next week!

-- 
Best regards,

Hi Graceson,

Sorry for taking so long to reply, I've had a busy couple of months.

The extension works for me, and the logs you list in your email seem 
fine to me, they're the same I see in projects I work on that use Psalm 
and the extension works fine.

 > I am running PHP 8.2.7, Nova 11.2 trial, and Psalm 
dev-master@2e8d575543c73bae8f9fd3ac46957699c0b90903.

I'm using PHP 7.4.33, Nova 11.3 build 534827, and Psalm 4.13.1. Not sure 
how outdated my Psalm version is, but that might be part of the problem. 
Seems a bit unlikely though since the output from the extension console