Forum Replies Created
-
Posts
-
'Support' wrote:
Try to change Font colors in TwilightColorMap, the problem will disappear if font colors are not default?
I changed the font color to clLime and the selected color to clRed. When I start the program and CS5 right after that, the font color is automatically set to the background color of the TActionMainMenuBar and you can't read the menu caption any more. Hovering over the menu item now, the selected background color changed from the original clRed to cl3DDkShadow, and the font color to clBlack. Even if I change the color of the TActionMainMenuBar to clSkyBlue, it turns into clBlack once Photoshop CS5 has been started. It seems as if the colors that are defined in the ColorMap are not recognized anymore, once CS5 runs. See attached screenshots. This only happens when using AC, and only with CS5!
Thanks.
Hm, what other information can I give you?
Graphics card: NVidia GForce 8600 GT (an old test system, I know…)
Driver: 266.58 (6.14.12.6658)
DirectX runtime version 11.0
The bug can be reproduced every time. It only occurs with Photoshop CS5, and only if I use AlphaControls.
No problem, here you go. Steps to reproduce:
Start Test.exe first
Start Photoshop CS5 (not CS3, which doesn't produce this bug!)
The 'File' menu item disappeared from the TActionMainMenuBar
Actually, the menu item does not vanish, as I found out, but something changes the highlight color of the menu item and the color of the menu font. If you remove all AC components from the project, the bug disappears.
Same here. I'm using the TV-b internal skin and see a white main form, a white caption bar and white TPanels every time my application starts up or creates another form at runtime.
Okay, I found it: CanDestroy. Can I leave both procedures below as they are or do I need to test for sFrameBar1.Items[0].Frame <> nil and then explicitely free the frame? There do not seem to be any memory leaks if I don't, but I want to make sure that it doesn't have any other implications when CanDestroy is set to false. Thanks.
procedure TForm1.sFrameBar1Items0CreateFrame(Sender: TObject;
var Frame: TCustomFrame);
begin
Frame := TFrame1.Create(nil); // <
do I have to check if the frame already exists before I create it?end;
procedure TForm1.sFrameBar1Items0FrameDestroy(Sender: TObject;
var Frame: TCustomFrame; var CanDestroy: Boolean);
begin
CanDestroy := False;
end;
'Support' wrote:The error occurs because frame is not created – frame is created immediately before opening.
Yeah, I know. Is there a way to prevent the destruction of the attached frame when I close (click on) an item?
Please find attached a little demo project. When testing, make sure that you navigate to a folder with a lot of files in it so that the vertical column scrollbar appears. That one is difficult to skin (I tried already and failed). Most of the component seems to work if you manually add TVirtualColumnModeview to the ThirdpartyList and set its Type of Skin to Listview (see attached image). Don't set it to VirtualTree though or you will get some weird behavior.
The Virtual Controls package has to be added from the Predefined Control Sets to the List of automatically skinned components, of course.
As a side note: the thread title is a bit misleading, because the component is now called VirtualColumnModeview. The name of its *.pas file is VirtualExplorerEasyListModeview.pas
Paulo, have you seen this one:
http://www.alphaskins.com/forum/index.php?showtopic=5379&view=findpost&p=31663
I experience similar issues with TThreads and TFrames.
'Support' wrote:Which Delphi version are you using?
D2007 Pro, all updates applied. To reproduce the error, you'll have to set TacSkinEffects -> AllowGlowing := True in the sSkinManager.
QUOTE (Support @ Aug 2 2010, 08:38 AM) <{POST_SNAPBACK}>Thank you, the problem will be solved in the nearest release.
Resolved in version7.03 beta. Thanks!QUOTE (Support @ Aug 2 2010, 08:36 AM) <{POST_SNAPBACK}>ExtendedBorders are used when this error occurs?
No, extended borders are not used. This bug is related, by the way: http://www.alphaskins.com/forum/index.php?showtopic=5458Please find attached a very simple test project. To reproduce the error, load an image into the ImageENVect and click with the mouse on the image until the scrollbars appear. Move either scrollbar with the mouse and watch how they behave. When you slide them to the left or right, the scrollbar buttons always return to their previous position. Clicking on the scrollbar itself shows the same behavior. If you disable skinning, the error disappears.
