Wifi Input Output bug

[enzyme69]

Sometimes, under circumstances, the Wifi Input and Output does not transfer. I tested in the setup like above.

Occassionally, when data is not right, Sverchok just does not bake and even the connection is remade, it stops working.

[ly29]

Test the following, restart blender and make that directly. Wifi needs a bit extra work.
The dictionary the wifi nodes use have two problems, it isn't reset on when opening a new file, it isn't multi layout aware.

[enzyme69]

I will keep eyes on it, seems the wifi can be pretty sensitive.

also I noticed the Viewer node when I use many, if one failed to work,
other will also stop working and to update is not always easy.

[ly29]

I will close this issue, added wifi to my todo.
Also made sure the dictionary is reset on file load, should help a little bit.

[enzyme69]

Thanks Ly.

[ly29]

Okay this is broken and I think it will go quicker and be better to rewrite this than to track down the problems.

[ly29]

This also has the advantage that we got rid of sv_Vars, a dictionary of the data in wifi nodes that isn't needed anymore.

[ly29]

There is actually an crazy amount of things that can go wrong for a simple node that only creates virtual links.
Many in nodes can have the same variable name, this isn't so good... Fixed.
Variable name in out node must match an input node.
Output socket must match input socket, and re order themselves.

I think how noodle reattach themselves have changed a little bit since 2.69 at least.

It is most working now, but perhaps not backwards completely compatible. Have to ensure that before pushing it.

And also the code is really ugly right now, has to sanitized a bit more, otherwise this isn't an improvement... Due to my dislike of how wifi in/out messes up the update system I haven't used so much recently so I am unsure about its correct behavior, have download an old sverchok and test a bit.

[ly29]

My favorite part is the new update function in wifi in, it has a good length

    def update(self):
        multi_socket(self, min=1, breck=True)

[ly29]

Partly changed paradigm how it works, I think this is a good idea.
For input you can set the var_name as the old ones did with.

For output you have to select var_name from an EnumProperty and click set to change it. To unlink an variable you have click reset.

Note Todos

1. Node colors are messed up - fixed now
2. The layout needs polishing.
3. Old layouts should continue working.

[ly29]

The amount of data has no effect on the time it takes to process the wifi node.
A cylinder with 100 verts and 100 subdivisions.

Updated  Cylinder in:0.1004
Updated  Wifi input.003 in:0.0001
Updated  Wifi output.002 in:0.0006
Updated  Viewer Draw in:0.045

[nortikin]

https://docs.google.com/file/d/0B6KMvjWAjGiyOURiOWZNU1JhSG8/edit
colors, yes. we need complex solution

[nortikin]

#120 (comment)

[ly29]

Yeah, as long as we make that optional and settable.

Is it okay if I make the wifi nodes brighter? The colors are kind of dark per default. Especially the node read/fail is very hard to read...

[nortikin]

yes, i'd like to change this colors too )) wifi not fits all concept

[ly29]

give me 2 colors and I will focus on the last bug before pushing the fix :)

[nortikin]

if you talking of two colors... than thae should be close
RGB:
0.674
0.242
0.363

0.536
0.242
0.674

[ly29]

I will push to refactor, it works for almost every case I try now

[ly29]

Please test a before pushing to master. Anyway it is working a lot better than before.

[nortikin]

oups

[nortikin]

nods[nod_name].update()

File "/home/nikitron/.config/blender/2.71/scripts/addons/sverchok-master/../sverchok-master/nodes/basic/wifi_out.py", line 140, in update
data = SvGetSocketAnyType(node, in_socket, deepcopy=False)
File "/home/nikitron/.config/blender/2.71/scripts/addons/sverchok-master/../sverchok-master/data_structure.py", line 1267, in SvGetSocketAnyType
out = SvGetSocket(socket, deepcopy)
File "/home/nikitron/.config/blender/2.71/scripts/addons/sverchok-master/../sverchok-master/data_structure.py", line 1342, in SvGetSocket
return out.copy()
AttributeError: 'tuple' object has no attribute 'copy'

[ly29]

Ooops indead

[nortikin]

oops is about my commit to master with your wifi )))

[ly29]

Simple fix however and should have been testeted before, give me 15 min or so and we push fix.
Can you share the file?

[nortikin]

https://drive.google.com/file/d/0B6KMvjWAjGiyRmE5WHNVZGh3aTg/edit?usp=sharing

[ly29]

I didn't get a tuple there so can't 100% confirm the fix, but it really should fix it

[nortikin]

hm, line is ok, but box is not

[nortikin]

it is pretty strange...

[ly29]

Hmm, strange that file seems to work for me. Did you get the fix from refactor?

[nortikin]

line gives tuples, but box gives lists!!

[nortikin]

and box not works

[nortikin]

yes, updated, it still not do

[ly29]

[ly29]

It is very strange.

[nortikin]

in morning maybe will be clear what is it

[ly29]

Sounds good, lets solve it tomorrow.

[ly29]

I still can't reproduce the bug. Anybody else?

[enzyme69]

There is a bug something about copy and tuple, it complaints.

Normally I use many wifi nodes, and only pipe in 1 values per node. But I realized we can pipe in many values and just wifi it. But that does not seem to work with Box node.

[ly29]

Okay I pushed-merged an update that should fix this specific problem.

[enzyme69]

Yes it is working now! Confirmed.

The update method is very smooth and interactive now. Who came up with this
brilliance. F8 to unzip and instant update via online. Great!!

---

• Jimmy Gunawan
  http://blendersushi.blogspot.com.au
  http://mayaspiral.blogspot.com.au
  http://houdoodles.blogspot.com.au
  http://puppetar.blogspot.com.au

[ly29]

Okay found and resolved it, don't think niki used the last update i pushed last night.

Note that the tuple on base level from box might expose some bugs in other places when one sets deepcopy=False in SvGetSocketAnyType. Exposing these bugs are good.

[ly29]

I think this works now, if somebody doesn't agree please reopen this issue.