-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
headerHozAlign not working #94
Comments
No we still use tabulator v4. So headerHozAlign is not available. |
Thanks for the info! Is v5 on the Roadmap? If yes do you have a rough estimate when you may be able to move to v5? (Just for me to know if I yet have to learn css...) Again thank you very much for your time you invested for this node - much appreciated! |
We did try to move but it broke a load of stuff, so that needs to get fixed up. Didn't seem to be trivial so who knows when we may get to it unless someone steps up. It's not a node I use day to day so not on my immediate roadmap. |
I am thinking about engaging. But I am a complete newbie to node-red node-maintenance. Where would I need to start? Could you point me in the direction? Some reads, videos? After the first dive I would estimate the amount of time I would need to invest and decide if it is feasible within my RL time constraints. Thank you!! |
Hi @akrea It is not terribly difficult but there are a few steps.
While I understand many of these steps may not be familiar to you, I have used terms you can search |
These steps I know as I am IIot software developer. But I lack knowledge of node-"Syntax" and a node-"how to". |
Hi
I have posted my issue on the node-red Forum.
In short: while the column options I tried so far work as intended, the option headerHozAlign has no effect what so ever. Since no one replied on discourse (although I did not give it much time). I thought I may post the issue here.
I have set up node red on the latest docker environment on an ubuntu server 22.04.
Installed is node red v3.0.2.
I use firefox browser in general but i have the same result on edge-browser.
The node version is 0.4.3
Thank you - great work anyway!
The text was updated successfully, but these errors were encountered: