Forum Replies Created
-
Posts
-
'minou' wrote:
Execute code When Page (Google Maps) Has Fully Loaded but this does not happen
Thank you :a3:, I'm sure Serge will answer this.
'Support' wrote:Hello
These skins were updated, look them:
http://www.alphaskin…s/blueglass.asz
http://www.alphaskin…/skins/sand.asz
http://www.alphaskin…skins/smoky.asz
I suppose the Sand skin is double :wacko:
I enlarged the sample with the BlueIce skin a couple of times, to show you the trouble with TcxSpinEdit:
[attachment=7203:EnlargedSpinEdit.jpg]
As you can see, the shadows and highlights of the buttons themselves interfere with the correct drawing of the arrows. Especially the Up arrow seems to be drawn too far up, thereby loosing its tip.
There are more skins (Smokey for example) that have similar trouble.
The new black box skin has arrows, that in TcxSpinEdit are hardly visible.
You have not reacted to my suggestion to change the two buttons of the TcxSpinEdit to one button with an up and a down side and one up/down combined icon. Because there's so little space, that might be better. That said, most skins work OK though.
Thanks!
'Support' wrote:Bright labels are worse than dark there, I think.
In that case, you should maybe withdraw the WOT skin. Even on panels, the texts are way too dim.
'Support' wrote:Do you think I must change an extension of such file? Or to add a some suffix to the file name?
Maybe suffix the filename with …_CS (Commercial Skin). So Metro DW would become Metro DW_CS. And since DW doesn't say much. Metro_CS would do it nicely.
'Support' wrote:Changes exists in this version of the package, but some skins should be changed or updated, seems.
I have equal images of TcxSpinEdit and TsSpinEdit in your test-app.
Look screenshots, is it correct?
They all look OK, except for the second one (the blueish one). Although its up/down arrows are complete, they are so crammed in their button surface, that they become misformed. That's why I suggested to combine the up/down arrows in one bitmap.
'minou' wrote:sWebBrowser1DocumentComplete not work correctly
If you want some action on this bug, you should be more informative about what goes wrong.
Please specify what the problem is.
'Support' wrote:I will prepare a special detailed article about protected AlphaSkins at the nearest days, please wait.
I've read the article. Maybe the filename of such skin should reflect the fact that it is protected. There's no telling now in advance.
To show you what I see on my display with the WOT skin, I made a picture with the brightness reduced:
[attachment=7177:LowLightsWOT.jpg]
As you can see, it is hardly readable.
'Support' wrote:Added in ToDo, but I can't say when these features may be implemented…
Version 10.11:
1. The checkbox flipping on double click works nicely now.
2. Positioning on a disabled line cannot be disabled.
'Support' wrote:Some improvements will be added in the v10.02
But some old skins must be updated (must be added or inproved UpDown skin section). I will do it later.
No change in v10.11
'mol' wrote:Well, that comes as a surprise…
I think you're under the impression that we plead for a freeware version of AC under Lazarus. But nothing is further from the truth. We think that a paid for, commercial package still has a large market in the Lazarus community, provided it has unique qualities. That is what AC has: there are no packages available in Lazarus with such a wealth of carefully themed controls.
I do not agree with the incompatibility argument. If the Lazarus environment was so different from a Delphi environment, the little test program that Serge included in his test library would not have worked at all. However after correcting the message parameter issue mentioned earlier, it does run. Not everything works as it should, but there certainly is a start.
'SzakiLaci' wrote:But he has a (genius) workaround-idea:
– compiling AC as a dll under Delphi > and writing a caller-class for it under Lazarus 😛
He's working on it since 2 weeks…
That may work for you, but it is not the general solution for getting AC to work with Lazarus. Because the reason for wanting it in Lazarus was, in the first place, the portability to all sorts of Unix and Linux systems..
'Support' wrote:Look, the “<-" button have same behavior as "CE", I will rename it to CE
But it's not the same function. The <- button backspaces the last entered digit. The CE button should clear the whole entry without affecting the current result (and the C button clears everything).
'Support' wrote:For changing of buttons looking will be added the new FlatButtons property.
Nice :a3:
'Support' wrote:I tried to change labels in these skins, but result is not better. Look attached skin as example.
It depends. When labels are placed on the form, it's much worse than when placed on a panel.
I also included the WOT sample. That's totally unreadable with dark text color.
[attachment=7085:DarkDarkGlass.jpg] [attachment=7086:LightDarkGlass.jpg] [attachment=7087:DarkWOT.jpg]
'Support' wrote:Thank you, I'll try make it.
Nicely dimmed text now :a3:
Maybe it's an idea to add a property in order to disable the possibility to position on a disabled checkbox. For instance add the property SkipLine in the DisabledKind property.
Also it would be nice if double click on the text would flip the checkbox.
'Support' wrote:TsWebBrowser component will be added in the AC v10.01
It works great :a3:
I think the places where the compiler switch ADDWEBBROWSER is used, can be eliminated.
'Support' wrote:Disabled glyphs are drawn as alphablended in the TsDBNavigator component, I don't know how to make it better.
Glyphs in DevExpress extracted from resources and painted by DevExpress, I don't know how to change them…
I looked into it. I don't see how you can change the images either. Only the TcxNavigator.Buttons.Images gives the possibility to create custom images. But they should not be used by AC for obvious reasons.
