Not sure if this issue has been addressed in previous post of if there's a workaround already. I'm using a laptop with a second monitor with Nexus Ultimate running on my laptop monitor. Dock is at the bottom and on auto-hide. When I'm working on my second monitor, the dock will not appear if I hover my cursor to the bottom of my first monitor. I'll have need to click on my first monitor (anywhere) before I can get the dock to appear. This is unfortunately a 2-step process to get the dock to appear and is very cumbersome. In fact, this decreases my workflow so much, I had to uninstall Nexus Ultimate.

Any solution to this?

Does this happen even if you are not running a full screen application on the secondary monitor? Please note that 'full screen' is not the same as maximized.

I'm asking this because Nexus disables edge bumps whenever it detects that a full screen application is running (so it doesn't pop-up in the middle of a game, for instance). When you click on the laptop's monitor, the full screen application ceases to be the foreground window and Nexus resumes responding to edge bump activations.

Is this what is happening?

I'm not running full-screen applications. Just maximized windows (e.g. Office applications, browser etc). But your description does sound suspiciously like it's detecting a full-screen application.

However, I have no problems whatsoever with Objectdock Plus.

Anyway around this problem? My Nexus Ultimate is still uninstalled - waiting for this issue to be resolved.

Well, you having Nexus uninstalled does not help me diagnose the problem so I can fix it, does it?

To fix something first I need to know what is causing it, so I can try and reproduce it here. In your case I need to know if the issue happens only when a windows is maximized on your secondary monitor (and not when there are no windows maximized), and it it happens with any maximized application or just with your browser window, for instance (e.g.; Chrome was notorious for 'appearing' as a full screen window instead of a maximized window when you maximized it).

Or the issue might have nothing to do with what I think might be causing it. The only way to be sure is for you to try what I described above and then report back.

Okie dokie. Will reinstall and get back to you. Indeed, I'm using Chrome. Maybe that's the culprit.

OK. Chrome is indeed the culprit. For all other applications, there's a slight delay in the edge bump if it's active on the second monitor as compared to the first monitor - but I can live with that. Would be great if that can be optimized.

Another issue which may not may not be related to Nexus. Kaspersky icon on the system tray cannot be right-clicked. All other system tray icons works.

Unfortunately, after I just freshly bought a license, I can confirm the problem. So far it is the exact same setup in my case - Chrome being maximised on the laptop screen, Nexus on my attached main screen, so activation fails when Chrome is maximised on the laptop screen and I come from there. Is there any way around this without letting ALL (pseudo-)full screen apps be interrupted by Nexus?

The Chrome issue had already been fixed some time ago, but Google changed the class name of the maximized window from 'Chrome_WidgetWin_0' to 'Chrome_WidgetWin_1' and so the fix stopped working.

I'm now detecting a maximized Chrome window by matching with 'Chrome_WidgetWin_?' instead (? being any character), so the issue should be fixed in the next release.

Hi Jorge,

thank you so much for letting me know. What would 'the next release' actually mean? More like days, weeks or months? I don’t know your update cycle so far .


All the best & have a merry Christmas

froschfinger

Usually there's a new release every 4 months or so, but there is no fixed schedule.

Anyway, I should be releasing a public beta of the next version just after Christmas.



Thanks, you too!

Hey Jorge,

that sounds real good . Will report in if the issue is resolved for me .

Just out of curiousity, if urgent bugs are found, would you offer intermediate fixes or would still stick to your about-once-in-four-month update routine ?


All the best

froschfinger

Oh I hate bugs. I will go out of my way to find them and fix them as soon as they are reported to me, provided I can reproduce them here, of course.

Most serious bugs are found almost immediately after a new public release because suddenly there are thousands of users running the software in very different configurations (compared to a handful of beta testers). During that initial period I will fix all reported bugs and issue a 'silent' release (i.e.; update files are replaced with newer versions without a public annoucement).

The window of opportunity for silent updates closes very fast though, since work on the next release starts almost immediately after. A lot of new features will then be 'under construction' and other bugs - which will mostly be caught later, still during the development cycle - might be accidentaly introduced.

Also, I noticed that many users dislike updates that happen too frequently, even though it benefits them.

If memory serves me correctly, there was only one time where I had to do an emergency release: when Weather.com changed their weather feed and the weather module suddenly stopped working.

That in turn prompted me to build a certain degree of redundancy so the weather module is no longer dependent on a single feed and that situation never happens again: if the main weather.com feed fails now for any reason, the weather module still has the MSN and Yahoo weather feeds to fall back on (besides the ever present and reliable METAR current conditions feed).

Hey Jorge,

that is real good news to me . Are you working full-time (and solo) on your software?

Haven't had any severe problems as of yet, but was a bit baffled that quite some smaller ones turned up just as I entered the Nexus universe. It however already seems quite stable and you really dedicated.

I am one of those enjoying frequent updates if they involve improvements and less new bugs, haha . I think I'd always favor that over infrequent ones while bugs or discomforts stick.

I actually admire people taking the beefs and challenges software development offers. I am developing websites, which doesn't feel half as challenging as software development. So: hats off, and keep it up :

Yes to both.



Most of the smaller bugs actually happen well AFTER that particular feature first gets introduced. When something new gets added, it is fully tested so the chances of a bug are really minor.

The problem is when more stuff is added later and some of the changes interact with code that was previously working fine in unforeseen ways. This is pretty common. Since it is pretty much impossible to test every single feature that was previously working fine (there are thousands of them, as you can imagine) for each release, sometimes something gets broken and this goes unnoticed because I and the beta testers don't use that particular feature.

Another problem is that some new users will notice these newly introduced bugs but then, more often than not, will fail to report them - perhaps in the incorrect assumption that the bug is too obvious (well, to them it is) or that nothing will be done about it.

Of what year? No, no, just kidding.