02-12-2022, 08:32 AM
Hi Jesse/team,
Any update on this, or - better - a fix ETA?
The root cause appears to have been identified over a year ago in the excellent post by microbug:
https://conductivelabs.com/forum/showthr...79#pid3179
Jesse's response, Dec 2020 - https://conductivelabs.com/forum/showthr...97#pid3197
"NDLR should easily be hostable by any embedded USB host out there that follows the 1.0 specs or later, and the fact that it isn't is, fundamentally a bug on the NDLR, not anything else"
We hear of bug/compatibility trackers, and we suggest enhancements, but there's little visibility into whether, or when, any bug/feature request/compatibility issue is ever going to be addressed. This is really frustrating, and leaves users feeling abandoned in spite of the efforts we make to test/document. We do get thanked, which is appreciated; but then we just wait...
From an unrelated feature request Aug '21 https://conductivelabs.com/forum/showthr...36#pid4836
"At this point we're not likely to be making any behavioral changes to the NDLR unless it is to fix things that are broken [...]" (looks like I'll never get the reverse-video display I suggested
).
It's OK to decide to stop development, we understand that. But if that's the really case then as a courtesy you should (IMHO) lock the Feature Requests sub-forum, and formally state that NDLR is now EOL.
However, it is NOT OK to let allow impactful, but well-characterised, bugs to persist for this long.
So for this (USB) issue, please:
- commit to a fix date; or
- commit to not fixing it
All the best,
auto
PS I still love the little critter, warts and all
Any update on this, or - better - a fix ETA?
The root cause appears to have been identified over a year ago in the excellent post by microbug:
https://conductivelabs.com/forum/showthr...79#pid3179
Jesse's response, Dec 2020 - https://conductivelabs.com/forum/showthr...97#pid3197
"NDLR should easily be hostable by any embedded USB host out there that follows the 1.0 specs or later, and the fact that it isn't is, fundamentally a bug on the NDLR, not anything else"
We hear of bug/compatibility trackers, and we suggest enhancements, but there's little visibility into whether, or when, any bug/feature request/compatibility issue is ever going to be addressed. This is really frustrating, and leaves users feeling abandoned in spite of the efforts we make to test/document. We do get thanked, which is appreciated; but then we just wait...
From an unrelated feature request Aug '21 https://conductivelabs.com/forum/showthr...36#pid4836
"At this point we're not likely to be making any behavioral changes to the NDLR unless it is to fix things that are broken [...]" (looks like I'll never get the reverse-video display I suggested
).It's OK to decide to stop development, we understand that. But if that's the really case then as a courtesy you should (IMHO) lock the Feature Requests sub-forum, and formally state that NDLR is now EOL.
However, it is NOT OK to let allow impactful, but well-characterised, bugs to persist for this long.
So for this (USB) issue, please:
- commit to a fix date; or
- commit to not fixing it
All the best,
auto
PS I still love the little critter, warts and all