Latest LCode version

[NEtech]

Try if this is different.
I cannot reproduce the problem on my computer.

 

[Badboy99]

Try if this is different.
I cannot reproduce the problem on my computer.

This version is working fine for me.
For reproducing you need a 4K screen.

I think you have changed (disabled) the high dpi awareness of the application.
This is a common way for legacy applications, which doesn't support the dpi scaling native.

EDIT:
One other thing. Can you please disable the automatic width expand for controllers >30 Byte or make it at least configurable.
This behavior is more then annoying.

Thx

 

[Badboy99]

@NEtech
I don't know, if you have seen my edit.

EDIT:
One other thing. Can you please disable the automatic width expand for controllers >30 Byte or make it at least configurable.
This behavior is more then annoying.

 

[NEtech]

Why is it annoying ?
It is >38
When the Coding is longer, you cannot see it!
Why not use the width available of users screen width.
It is not full screen and the height is also smaller as the old LCode.
But here you have version where you can change value in ini file.
Latest version is here.

{2.0.2}
{Changed HD screen behavior - test}
{Changed language menu and language ini}
{Change to max width if Coding is above 38 Byte is configurable - ini file}
{MaxCodewidth=38 in ini file is standard}

 

[Badboy99]

Thank you very much :-)
The latest version with the configuration option is perfect for me.

Usually I have other programs beside VCDS open. The "not filling" mode of LCode saves the position and restarts exactly at the position I have closed it before.
With the "filling" behavior the LCode always starts at position 0,0 and hides everything else.
When I move it, the width gets reduced and everything is fine. But I have to do this everytime when I start the LCode from inside the VCDS.

My new setting: MaxCodewidth=200

And btw. who reads a coding value with more then 30 (or 38) bytes as a string.
I'm not able to do this. ;-) The direct selection of a byte is there much more helpful. Thanks for this improvment.

 

[Sebastian]

{2.0.2}

Minor note, the EXE file version claims to be 2.0.1, the application title bar says 2.0.2. No need for a fresh file, unless you insist.

 

[Uwe]

That's true, but I'm not a fan of hosting pictures externally.

And we are not a fan of being our users' photo hosting service.

-Uwe-

 

[Sebastian]

Can't resist but quote you Uwe: "What's with that we sh** Kimosabe?"

 

[NEtech]

Latest version is here.
{2.0.4}
{Use same Coding in LCode 2, if LCode is from VCDS}

 

[hadez16]

Am I missing something or is there no highlighting when using the search function?

 

[NEtech]

Found Bytes are showed in the statusbar and change position to first found Byte.

 

[hadez16]

Aaahh, didn't notice the statusbar, thanks!

 

[NEtech]

Latest version is here.
{2.0.5}
{4 pull-down boxes are now possible instead of max 3}
{If more than 1 Byte is found from search, Ctrl arrow up/down jump to next found Byte}
{2.0.6}
{Not important}
{Dutch translation}
{French translation}
{Chinese translation}
{Correction for search Ctrl Up/Dn}