Forum Replies Created
-
AuthorPosts
-
HeDiBoParticipant'Support' wrote:
Yes, I'll try change it tomorrow.
Not quite as nice as it could be.
If you change the SkinSection on the buttons to simple BUTTON, the result looks much better.
Then adding the Clear Entry (CE) button (clears only the current input, not the calculated result sofar) will make it look like this:
[attachment=7083:acCalcEdit.jpg]
Also, the TsCalcEdit component should have a mode to display the results with a variable number of decimals.
HeDiBoParticipant'Support' wrote:Hello, Dick! These contrast changes were added to original skins, try them.
I think, these changes are really needed and duplicated “_contrast” skins were removed.
Hi Serge,
Most are correct now, since they are still well readable in low contrast :a3:
A few skins are still problematic: the label text should be bright in stead of dark in the following skins:
DarkGlass, Nautilus, Rhombus and WOT,
With the dark texts, they are hardly readable.
HeDiBoParticipant'Support' wrote:These bomb attacks happens every week.
I didn't know that. I sympathize with you. Keep it up and cheers.
[attachment=7072:T13S100B.jpg]
HeDiBoParticipant'Support' wrote:Hi, maybe I not quite understand an issue. Look attached recompiled demo, this is what I have.
All right. Choose the BlueGlass skin. See that the up/down buttons are too small to accommodate clearly visible arrows/triangles.
Therefore I suggested to combine up/down icon in one icon with special processing according to the location where the icon is clicked.
PS. How are things in Odessa? I heard about the bomb attack. Must be disturbing.
HeDiBoParticipant'SzakiLaci' wrote:4. Example project compiles successful (no skins yet) > but when I try to move the window > error:
Code:Project project1 raised exception class 'External: SIGSEGV'.
In file 'sSkinProvider.pas' at line 7550:
if (TWMWindowPosChanged(Message).WindowPos.Flags and SWP_HIDEWINDOW = SWP_HIDEWINDOW) {$IFDEF D2011} and not Application.Terminated{$ENDIF} thenThe problem stems from this code:
Code:Source: wincontrol.incprocedure TWinControl.SendMoveSizeMessages(SizeChanged, PosChanged: boolean);
var
SizeMsg : TLMSize;
MoveMsg : TLMMove;
//Flags: UINT;
begin
if (not HandleAllocated)
or ((not SizeChanged) and (not PosChanged)) then exit;Perform(LM_WindowposChanged, 0, 0); <— Causes the access violation
The message is LM_WindowposChanged with an LParam of 0. That causes an Access Violation in TsSkinProvider. This code fixes that:
Code:procedure TsSkinProvider.AC_WMWindowPosChanged(var Message: TMessage);
begin
if Assigned(SkinData.SkinManager) and // *** DB ***
acLayered and // *** DB ***
DrawNonClientArea and // *** DB ***
( Message.LParam 0 ) then begin // *** DB ***
if (BorderForm nil) and Form.HandleAllocated and IsZoomed(Form.Handle) then
FSysExHeight := ActualTitleHeight > (SysCaptHeight(Form) + 4)
else
FSysExHeight := False;Sorry for the misalignmment, I cannot get it right.
HeDiBoParticipant'Support' wrote:Hello!
I have tested it with DevExpress v12.1.6, 14.1.2 and newer. I will try it with old version now.
Also, checked with DevExpress v6.54
I use DevExpr v11.2.9 (v2011 vol 2.9)
But I don't think it has much to do with the DevExpr version.
HeDiBoParticipant'Support' wrote:TsWebBrowser component will be added in the AC v10.01
Very nice :a3:
March 1, 2015 at 1:41 pm in reply to: DevExpr TcxCheckListBox lines are too close to each other #53161HeDiBoParticipant'Support' wrote:Can you show a screenshot, please? Because I not quite understand the issue, seems.
As you can see, the checkbox with label “I should be disabled” looks disabled in TcxCheckListBox, but does not look disabled in TsCheckListBox, because the only difference is a subtle change in drawing of the box, but not of its label:
[attachment=7055:DevExprCLB2.jpg]
HeDiBoParticipant'Support' wrote:Hello, Dick
I can send it if you want, but this package doesn't work yet.
It is may be installed under Lazarus now, but many things must be changed for work with these components.
Hi Serge,
That's why I offered my support. I'm a pensioner with lots of free time and 45 years of IT experience. So I would like to have a crack at it (free of charge of course 😉 ).
You mentioned to have a specific problem, that hampered further development. Let me know by PM what that problem is, so I can examine it.
HeDiBoParticipant'HeDiBo' wrote:So, what we really want is a TsWebBrowser component. Then only projects needing web browsing will bring in the libraries needed for that.
No progress on this front in AC 9.20 :a1:
February 19, 2015 at 4:20 pm in reply to: TsDBGrid row and column lines too pronounced in dark skins #53108HeDiBoParticipant'Support' wrote:I'll check it.
Solved in 9.20 :a3:
February 19, 2015 at 4:17 pm in reply to: DevExpr cxDBNavigator does not look right in dark skins #53107HeDiBoParticipant'Support' wrote:Will be fixed in the nearest release.
It's still a mess in 9.20:
[attachment=7041:DevExprDBNavigator.jpg]
In TsDBNavigator, disabled buttons in a dark skin are invisible. However, in TcxDBNavigator these buttons really stand out, because the dimming is incorrectly skinned.
HeDiBoParticipant'Support' wrote:Thanks. Will be fixed in the nearest release.
Not fixed in 9.20 :a1:
HeDiBoParticipant'Support' wrote:Yes, I have not found a way how to change this color still.
No change in AC 9.20 :huh:
February 19, 2015 at 3:05 pm in reply to: DevExpr TcxPageControl tab headers unreadable in dark skins #53104HeDiBoParticipant'Support' wrote:I'll check if it's possible to change font there.
Solved in 9.20 :a3:
HeDiBoParticipant'Support' wrote:I'll check it soon also.
Solved in AC 9.20 :a3:
With SkinManager.Options.ChangeSysColor = True it does even look better!
February 19, 2015 at 2:55 pm in reply to: DevExpr TcxCheckListBox lines are too close to each other #53102HeDiBoParticipant'HeDiBo' wrote:No changes in AC 9.15 :huh:
No changes in AC 9.20 :huh:
HeDiBoParticipantProblem is solved with SkinManager.Options.ChangeSysColors setting :a3:
HeDiBoParticipant'HeDiBo' wrote:The answer must lay in the possibility to change the system highlight color. I'll study that.
Problerm is solved with the SkinManager.Options.ChangeSysColors property.
HeDiBoParticipant'Support' wrote:I will check it now.
No change in 9.20
-
AuthorPosts