Matrix user forums

I anybody else having same problem,the new gui seems to be very heavy,when i move the mouse cursor over the fc4 gui,it takes 50-90% cpu load..
Tested in 2 mouse,the Thinkpad own trackpoint and Logitech cordless mouse.. My laptop is not very powerfull (P4M 1.8GHz) but still.. At Flow code 3 moving the mouse cursor takes only 2-7% cpu load... And resizing the component panel could cause Fc4 take 20-30% cpu load even when it does nothing.
Havent tested at my other pc yet,dont have time to install flowcode4 at that pc
Are there plan to do that monocrome glcd a "real" component,so it can be simulated? Because it helps a lot to when you dont need the download program every time when you make changes or new display code...

The GUI has been re-engineered and it will take up more CPU time, but the effect should not be too much. I've just tested here with my three and a half old PC (with a 3GHz P4 processor) and it doesn't go beyond 50%. Also, the same program in V3 has the exact same percentage.

I was only getting 50% when the program was simulating. When it is running normally, the percentage is close to zero. Is there something in your program that is particularly resource-heavy? Perhaps you should send me your program so I can see how it behaves here.

We have considered a mono gLCD component, but there are so many types that it is difficult to decide which one we should support. Do you have a specific gLCD in mind?

I test the gui on my desktop pc (core2duo 2.8GHz)when i had time,and get back then...
What comes he monocrome glcd,i think there is two common controllers, Samsung ks107/108 and Toshiba t6963..
The displays with ks108 controller are very cheap,you can get 128x64 display on 15$ on ebay..
You had custom code ready for ks108 (and i had modified code,witch works on 192x64 displays,if you need,i can sent the modified code for you). So all that ks108 need is the component for simulation..
By the way,the custom code for ks108 had bug,if the number on print number macro is 10,100,1000 etc. it drops the last 0 off,and displays 1,10,100,if i remember right,the bug is in string length code,witch makes stringh length bigger when the number is bigger than 10,100,1000,instead 9,99,999..
So those 2 controlles is the top of the "wishlist",ks108 most,then t6963,of course both is better ..
The displays on t6963 are more expensive,the controller is newer and goes at least 128x256 resolution,while Samsung needs one controller per 64x64 pixels.