-
Notifications
You must be signed in to change notification settings - Fork 233
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
idea for text viewer #894
Comments
you want to autosplit the (nodeview) to (textview+nodeview) ? and select the textblok of the newly created textview to match the textblok that the ViewerText is writing to? simple Tickbox for ViewerText to turn on/off auto updates, and make ratelimit the update frequency,... like .. 'if last update < 0.2 second skip this update` |
if so.. perhaps may help: https://github.com/zeffii/BlenderPythonRecipes/wiki/Areas |
nonono, easier. Ctrl+J frame will contain text from sverchok viewer text file. no need areas |
so nodeview will contain text in frame |
oooh. i read incorrectly, literally the Frame . i see :) cool :) |
but autoupdate is needed, as sthetascope do maybe. or leave button... |
so, ViewText is added and it Auto packs itself into a Frame? |
that is question. where to put frame? maybe separately add as empty or to add framed text viewer + size |
additionally adding text viewer need to initiate text file |
I like this.. difficult to decide, but I think option to 'Frame Me' would be neat for ViewerText , it would then autoset the Frame.txt to the correct one. |
or... define minimum velues left-up and add frame to leftest uppest corner once and leave it alone. We can additionally add form to describe layout in some text, adding header and description in upside of layout. auto-typography. this may be contained in some meta-data of layout and import-export. than added when importing. |
if you |
well I see your point, but you can |
but you are right, it does not need to autoframe the ViewerText.. |
https://gist.github.com/nortikin/4852a618a14d9dfe439bafc2ff6c0c13 |
this is ugly, it moves with new node |
maybe better to add this node at layout creation... but how? |
There is no constructor for Layouts.. We wanted this to force an automatic User for each new layout. The only useful suggestion was to create an operator replacement for making a new node tree.
|
@nortikin don't use underscore in classname/ bl_idname for the node |
I use name instead. |
pitty Frame doesn't do syntax highlighting :/ |
got it about underscore |
I admit we ned separate button for this frame stuff and so on. |
for convenience bl_idname and classname are identical for all nodes. (I think). I'm not sure we can override default ops like |
so, for now viewer text makes Frame at button pressing. |
By any chance, the viewer, can it be multi row and column with numbers
like Excel spreadsheet? Depending on how many data plugged in?
|
@enzyme69 do you mean text have to look like: vertices | pols/edges | matrices
=1= | =0= | =1=
() | | ()
() | | ()
() | | ()
() | | () ? |
the text from text area will looks like:
or
|
or to break data that longer than frame height? |
Hmm... in a way that we can see all in one window not scrolling to find On Monday, 3 October 2016, nikitron notifications@github.com wrote:
|
it is hard. Font in blender is not monospace i guess. |
I see... become comma/space/tab separated value is fine.
|
ok, patrially text out node's functionality can be supported, but hey, why not upgrade text out node itself? we can use it to make csv file that updated every time (with boolean active) with form of data you ask now. How do you think? It is not matter of frame text, but of csv format. |
Sounds good to me!
|
Dealga thought of it as i see from comments in code. |
to create Frame for inserted ViewerText node that binded automatically to Sverchok viewer text file. So user can view automatically, no need to open text window. But question is size of frame and where to post it and if add new viewer, we not need to add new frame. And when removing last viewer, should we remove frame (i guess not)?
That is simple improvement, i think.
The text was updated successfully, but these errors were encountered: