TUniSyntaxEdit Bug

[freedowsRoO]

Hello! How are you??

The TUniSyntaxEdit  has a bug that the layouconfig.width = 100% doesn't work.... I also tried to set the aligment = AlClient and doesn't work.  Can you check this please?

[Sherzod]

Hello, 

Fine, thank you. And you? 

1 hour ago, freedowsRoO said:

The TUniSyntaxEdit  has a bug

Which build are you using? Can you make a simple testcase for reproduce? 

[freedowsRoO]

2 hours ago, Sherzod said:

Hello, 

Fine, thank you. And you? 

Which build are you using? Can you make a simple testcase for reproduce? 

Sure, here is it.

Version: 1.90.0.1496

syntaxEdit.rar

[freedowsRoO]

Up

[Sherzod]

5 hours ago, freedowsRoO said:

Up

Hi,

Sorry for the late responce.

I will check it again.

[Sherzod]

On 3/11/2020 at 6:50 PM, freedowsRoO said:

Can you check this please?

Hello,

Maybe something like this at the moment?

CustomCSS:

.CodeMirror-wrapping {
    position: relative !important;
}

 

[freedowsRoO]

17 hours ago, Sherzod said:

Hello,

Maybe something like this at the moment?

CustomCSS:

.CodeMirror-wrapping {
    position: relative !important;
}

 

Yep!! It works! Thanks!

[Pep]

Hello,

TUniSyntaxEdit has a side effect. The side effect is that it changes the default Cursor (crArrow) and changes it to (crIBeam) for the rest of the components of the entire application.

Sample 1) TuniPanel and TUniSyntaxEdit:

Look the cursor, when is over the panel it shows a clBeam.

 

Sample 2) TuniPanel and TuniMemo:  

Now over the panel the cursor is crArrow 

Note: do not forget to remove from the uses clause "uniSyntaxEditorBase, uniSyntaxEditor" units that is causing the side effect.

You can use the same test case from avobe previous post.

Can you check this please?

 

[Sherzod]

1 hour ago, Pep said:

TUniSyntaxEdit has a side effect. The side effect is that it changes the default Cursor (crArrow) and changes it to (crIBeam) for the rest of the components of the entire application.

Hello,

But not for all controls, right?

[Pep]

Yes you are right, not all controlls.

In my case it happens in TuniPanel and TuniURLFrame (which is my main component in this app).

There is a workaround? if not, don't worry, i would change the TUniSyntaxEdit by TuniMemo.

Thanks.

[Sherzod]

7 minutes ago, Pep said:

There is a workaround? if not, don't worry, i would change the TUniSyntaxEdit by TuniMemo.

Hello,

Can you use UniSyntaxEditEx instead?

[Pep]

Yes , with UniSyntaxEditEx the cursor works fine! 

but now I have the problem of layoutconfig of TUniSyntaxEdit:

On 3/11/2020 at 2:50 PM, freedowsRoO said:

Hello! How are you??

The TUniSyntaxEdit  has a bug that the layouconfig.width = 100% doesn't work.... I also tried to set the aligment = AlClient and doesn't work.  Can you check this please?

 It seems this CustomCSS doesn't work with UniSyntaxEditEx :

On 3/17/2020 at 5:09 AM, Sherzod said:

CustomCSS:

.CodeMirror-wrapping {
    position: relative !important;
}

 

Thanks!

[Sherzod]

1 hour ago, Pep said:

 It seems this CustomCSS doesn't work with UniSyntaxEditEx :

On 3/17/2020 at 9:09 AM, Sherzod said:

I will try to analyze.

[Sherzod]

3 hours ago, Pep said:

 It seems this CustomCSS doesn't work with UniSyntaxEditEx :

On 3/17/2020 at 9:09 AM, Sherzod said:

One possible solution.

1. CustomCSS:

.CodeMirror {
    width: 100% !important;
}

2. UniSyntaxEditEx1.LayoutConfig.Width = 100%

[Sherzod]

3 hours ago, Pep said:

 It seems this CustomCSS doesn't work with UniSyntaxEditEx :

On 3/17/2020 at 9:09 AM, Sherzod said:

Or just use:

UniSyntaxEditEx1.LayoutConfig.Width = 100%

[Pep]

13 hours ago, Sherzod said:

One possible solution.

1. CustomCSS:

.CodeMirror {
    width: 100% !important;
}

2. UniSyntaxEditEx1.LayoutConfig.Width = 100%

Hello, with these parameters, "UniSyntaxEditEx", still does not fit the window correctly.

 

Attached test app in case I'm doing something wrong.

Thank you!

syntaxEdit.7z

[Sherzod]

56 minutes ago, Pep said:

Hello, with these parameters, "UniSyntaxEditEx", still does not fit the window correctly.

Well that's right, it only affects the width.