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}

 

[paulwhite09]

NEtech - FYI

VCDS 21.3.0 Bug in LCode address 09 BCM Central Elec.
Byte 17 - Bits 1 and 2 - check boxes and descriptions do not line up but are still linked and active.

 

[Sebastian]

VCDS 21.3.0 Bug in LCode address 09 BCM Central Elec.
Byte 17 - Bits 1 and 2 - check boxes and descriptions do not line up but are still linked and active.

Can you include a screenshot please? We need to know which version of LCode you are using, as well as what the current coding is and what label file is used. So ideally, an Auto-Scan would help a lot to reproduce this.

 

[Dana]

@paulwhite09 and @Sebastian , I believe Paul's LCode was full-screen because I simulated this on my bench and it was OK using the default size. Paul's screen shot:

New photo by Dana Smetanick

photos.app.goo.gl

My bench simulation with that BCM1 4H0-907-063-V1 label loading using 2.0.5:

New photo by Dana Smetanick

photos.app.goo.gl

LCode does get goofy when I full screen it on my 4K desktop display.


Address 09: Cent. Elect. (J519) Labels:. 4H0-907-063-V1.clb
Part No SW: 4H0 907 063 CG HW: 4H0 907 063
Component: BCM1 2.0 H12 0130
Coding: 06002091063C9FE08100088380003928CF9CD208A6090221000004406000


Edit, I cropped it so the photo wasn't so massive but the full screen (using my Bench 01 coding) looks like:

New photo by Dana Smetanick

photos.app.goo.gl

I get the same bit shift with 2.0.6.

 

[NEtech]

I fix that, the anchors on the Bit 1 and 2 lines are wrong.
I better remove the maximize icon, I see no need to change to max screen size.

 

[hadez16]

Is it possible not to close other LCode.exe instances when closing the LCode instance that was opened via VCDS?

There are situations where I have several LCode instances opened while comparing codings from several other customers, and committing a new coding by closing "the LCode from VCDS" closes all other LCode instances too.
That is quite annoying.

EDIT: after thinking of it for a while, this could be more a VCDS-thing than a LCode-thing?

EDIT2: these other instances were not started via "LCode 2" button but independently

 

[NEtech]

EDIT: after thinking of it for a while, this could be more a VCDS-thing than a LCode-thing?

No it is not a VCDS thing, user has to close LCode, to get the new coding to VCDS.

My left hand is always close to the ESC key, so it does not take long clicking ESC some times.

 

[hadez16]

I have to correct myself: What I mean is, that ALL LCode instances are automatically closed when you close the coding dialog in VCDS.