Matrix user forums

Hallo Benj

In single steep simulation in v4.1 show the local variable if i select in the macro.
If i test again,the variable i must select again.I think if i select a lokal variable then alltimes in the macro i can show thame as in V3)

The NOT funktion dont work in simulation.

You have got a dp in variable name, which means you have created it as a local variable by macro ,so if you are not within that variable, then that local variable would be invisible to your variables list....i believe.
Sorry if I miss understood
Re: NOT,
(~ = bitwise NOT) Excuse the pun..... NOT sure on that one
I would have expected answer to be 15. that's if it is treated as a byte.
However if treated as floating point ( i think) then
~ 240 = 1111111111111111111111111111111111111111111111111111111100001111
So how would a byte of this value be treated?
If you assign a 32bit 1111111111111111111111111111111111111111111111111111111100001111 to a 8 bit variable e.g. test, then look at the value of test in variables window you will see what I mean.
Personally perhaps you are correct and ~ is being treated incorrectly. I wounder what maxtrix will say.. They will probably say I'm talking nonsense :p

Hello medelec35

Yes i now ,the locale variable you can show only if you work within that macro,but if i have select the variable and i start debug again,the local variable
dont come automaticly again if if you work within that macro,i must select again.For 1 or 2 variable it is ok,but if you have more than 1,i must do
"click" very often for debugging.

With the "NOT" i be aware it,my in V3 running ok project ,in V4 have a bug.The attachment code is only for demonstrate it.

I mean,i can have full concentration of my extensive project only,if i now,"flowcode work ok",but otherwise i must show,if my code dont work,is the bug
in my code ore a bug of flocode.

I think also the beta test ,2 days is to short!

Regards wolfgang

saschech@gmx.de wrote:I think also the beta test ,2 days is to short!

I totally agree. People who work full time in other jobs won't have the time over a two day period (less of you add total hours up) to check for bugs. I wounder how long V4.0 was beta tested for? Somewhere in V3 forum, it was suggested by a member of matrix staff that time
At least a week minimum I would say.
for beta testing could of been too quick.

Hello

No answer from matrix, so i have three alternative:

i change all my "NOT" with XOR 0xff,

i work with V3

ore i wait and hope..............

Hello

Sorry the NOT problem has been added to our bugs list.

For now the XOR 0xFF should work fine.

Sorry for any inconvenience caused.