Good morning fellow B4X'ers,
So I've got to start a new project for a new client in the next few weeks, but the client specifically requested that the project be developed using #C, the answer is yes I can do that if need be.
I would personally prefer to use B4J for this project as VS DataGridViews are nowhere near as light weight as they should be in my opinion and also not as fast either. I personally find that DataGridViews do not initially populate nearly as smoothly as B4X xCLV with my modified lazy loading routine which loads 1000 results at a time, but the client is insisting on C# so sadly that's what they will get.
An hour ago I decided to create 3 simple For Loop test programs just to see just how quickly C#, VB.Net and B4J can run a counter in a label counting from 0 to 100000. B4J is using Sleep(0) whilst both C# and VB.Net are using Application.DoEvents() to keep the programs responsive. Yes I know I could have used async with await instead, but I didn't.
PLEASE NOTE: The counter speed is processor dependent, this was created on my spare laptop.
Enjoy...
So I've got to start a new project for a new client in the next few weeks, but the client specifically requested that the project be developed using #C, the answer is yes I can do that if need be.
I would personally prefer to use B4J for this project as VS DataGridViews are nowhere near as light weight as they should be in my opinion and also not as fast either. I personally find that DataGridViews do not initially populate nearly as smoothly as B4X xCLV with my modified lazy loading routine which loads 1000 results at a time, but the client is insisting on C# so sadly that's what they will get.
An hour ago I decided to create 3 simple For Loop test programs just to see just how quickly C#, VB.Net and B4J can run a counter in a label counting from 0 to 100000. B4J is using Sleep(0) whilst both C# and VB.Net are using Application.DoEvents() to keep the programs responsive. Yes I know I could have used async with await instead, but I didn't.
PLEASE NOTE: The counter speed is processor dependent, this was created on my spare laptop.
Enjoy...
Last edited: