LabVIEW
LabVIEW Roadmap (2022)
@GGT wrote:
I (and I'm sure many others) welcome the long overdue introduction of a Data Grid control, although I'll have probably retired before I see it. Better late than never, I suppose.
I hope they'll ask for advice on the grid control.
I also made one. I get a feeling that a native grid control just won't be able to do what I'm doing.
One of the things I require, is to be able to add my own "controls", like: custom color pickers (don't get me started), line style and width, point style selection (picture rings are rather ugly), etc.
Making custom popups (like a custom color picker) behave like the build in popups (colorbox, enum, ring, combobox) is extremely challenging. Esp. if it needs to behave with modal parent windows.
Until we're able to make controls that do what NIs controls do, we're limited to those controls. And a grid control won't be nearly as powerful as I (and my customers) would like.
Search LabVIEW like a graph! 
wiebe@CARYA wrote:
@GGT wrote:
I (and I'm sure many others) welcome the long overdue introduction of a Data Grid control, although I'll have probably retired before I see it. Better late than never, I suppose.
I hope they'll ask for advice on the grid control.
I also made one. I get a feeling that a native grid control just won't be able to do what I'm doing.
One of the things I require, is to be able to add my own "controls", like: custom color pickers (don't get me started), line style and width, point style selection (picture rings are rather ugly), etc.
Making custom popups (like a custom color picker) behave like the build in popups (colorbox, enum, ring, combobox) is extremely challenging. Esp. if it needs to behave with modal parent windows.
Until we're able to make controls that do what NIs controls do, we're limited to those controls. And a grid control won't be nearly as powerful as I (and my customers) would like.
Fully agree here. When I designed mine I needed very specific variable types. They were displaying a memory map and doing checksum calculations, so I couldn't just use a double to represent any number. It needed to be a bit-perfect match to the memory it was displaying. No other datagrid that I found (like the Qcontrol example one or the .net one) had enough customization over data types, so I had to make my own.
@TiTou wrote:
@EricR a écrit :
NI created this view so that we could specifically share with all LabVIEW users. We agree that showing this in some way is a useful communication tool.A pdf is a snapshot, it's barely better than nothing, I expect much more from NI.
A snapshot is up to date only the day it's published and will inevitably become obsolete, show more love to the community, create a page ni.com/roadmaps and keep it up to date.
Once gRPC is ready, we could have a gRPC interface to the current roadmap 😁.
@Intaris wrote:
@TiTou wrote:
@EricR a écrit :
NI created this view so that we could specifically share with all LabVIEW users. We agree that showing this in some way is a useful communication tool.A pdf is a snapshot, it's barely better than nothing, I expect much more from NI.
A snapshot is up to date only the day it's published and will inevitably become obsolete, show more love to the community, create a page ni.com/roadmaps and keep it up to date.
And as such, the PDF really should have a date so that we can judge how likely the data is to be relevant or not. I'm assuming there'll be more versions of this in future?
I might be asking for a bit much here, but it would also be nice to see how well NI holds to the roadmap. It could be something as simple as "We planned for X in Q2 2023, released in Q4 2023" with a 2-3 sentence description of the released feature. Just holding the last 3 years' worth of releases would be nice. I tend to upgrade every 3 years, so this would help in seeing what new features I could use.
