Forum Replies Created
-
Posts
-
Yes. The Project option (Project – Options – Packages – Build with runtime packages).
I could understand this somewhat, if the phenomena also occurred when running the app outside the IDE. Because I used Quality Central bug reports to edit the VCL. Those patches are not used when using runtime packages. But why does it go OK then outside the IDE?
I'll send you, by separate mail, my version of Form.pas When you search the file for the string “qc” you'll find all the patches applied.
'Support' wrote:Sometimes I see a blinking of the title after the button clicking. You meant this blinking?
The strangest thing :wacko: : the problem only manifests itself if the project runs under the Delphi IDE (I still use Delphi 7). If you run the program stand-alone, the problem disappears :a1: The problem can be seen in the first image of the original topic. It shows a form caption that is not skinned at all.
I did some more testing and found that only if I build the test project without packages, then I get the problem but only when running in the IDE.
Although this now turns out to be a corner case, it might point to a potential problem that will surface in some circumstances.
'HeDiBo' wrote:Sure. Here it is:[attachment=4914:FormCaption.rar]
If you set ExtendedBorders to True, the problem goes away.
I'm working on Windows Vista, Vista themes enabled.
Sorry to find it isn't solved in 7.44. 😡
Quote:Can this effect be reproduced in a new application?Sure. Here it is:
[attachment=4914:FormCaption.rar]
If you set ExtendedBorders to True, the problem goes away.
I'm working on Windows Vista, Vista themes enabled.
'IPSteven' wrote:If the function's name mimics that of a standard Delphi function, in this case sMessageDlgPos() vs MessageDlgPos(), it should have the same functionality or else it appears that something in AlphaControls is broken.I agree. In fact, if skinning is off, the function should not go to a standard Windows function, but to the Delphi MessageDlgPos function :wacko:
'deep_blue' wrote:I am not angry with Serge and also I waited some replies for one weak for this topic. I also know that serge is very polite, but this is my way and my english…
You misunderstood. The point is, that your post in this forum does not help other users, because they are not able to find it. Therefore, the forum requires that you make a new topic for each of your questions or issues.
You started off with three issues, numbered 1 to 3. Because they could not be described in one sentence, you named your topic “bugs”. In that way you made it impossible for other users with similar issues to find the answers from support.
Hence: start a new topic for each question or issue.
And a merry Christmas to all 🙄
Because this forum is to for all AC users, and not just for you, you should make a different topic from each question or issue that you have. In that way other users can benefit from it, because the topics can then be found by the appropriate keyword. Your topic is “bugs” which is not descriptive at all.
Please, adhere to the forum rules of a forum you apparently depend on.
Serge is too polite to make this point strongly. So I do it for him.
'carlosig03' wrote:DevExpress 6.54 Not supported in ALphacontrols 7.26 at runtime.
What I do is leave the setting {.$DEFINE DEVEX} in sDefs.inc alone. Then in projects that need Developer Express, I define the conditional DEVEX in the project definition.
Just compiled an application in this way. Works like a charm.
'Glinco' wrote:Great. It works!
You're genius.
Nothing genius about it. I just had similar problems and started to google.
'Glinco' wrote:Ok, let's in English.
When I try to start program with SkinManager in it, it falls with Runtime error 216 before line Application.Initialize;.
I have problem with debugging in Delphi, when I include module sSkinManager in simple default Windows Form project (in uses clause of main form).
Form is empty, just add “uses sSkinManager”.
With Intagrated Debugging option set to off everything is ok.
Program starts from explorer correctly and works fine.
Delphi 2010 with Updates 4 and 5.
I saw this before, but don't remember how it can be fixed. 🙁
Try to disable your virus scanner. If that is the cause, have a look at this: http://forum.antivir.de/wbb/index.php?page=Thread&postID=1031695
'Glinco' wrote:С некоторых пор при отладке из Дельфи 2010 стала появляться ошибка “Runtime Error 216 at 004050AE” на этапе запуска программы.
Без отладки сама по себе прога запускается нормально. Перерыл инет – нет четкого ответа.
Делал простой проект – пустая форма. Без модуля sSkinManager в разделе uses все работает. Как только добавляешь его туда – ошибка и прога не отлаживается.
В чем может быть причина?
Спасибо.
Please, post these messages in the Russian part of this forum. We, mere mortals, cannot read your script.
QUOTE (Support @ Aug 21 2010, 06:44 AM) <{POST_SNAPBACK}>HelloThank you for screenshots. Which HP printer you have installed?
I'll try to install drivers and I will look this dialog on my PC.The printer is a HP Color Laserjet CP1515n PCL 6 used over the internal network.
QUOTE (Support @ Aug 6 2010, 08:38 AM) <{POST_SNAPBACK}>Can you verify this dialog in the ASkinDemo.exe version 7, please? Many changes were made in the v7 and problem may be solved already.
And can you show me a screenshot of dialog?You can disable srStdDialogs property before dialog showing and enable it after dialog closing. This dialog will not be skinned in this case.
These are the PrinterSetup screens for version 6 and version 7. They have exactly the same flaws:
[attachment=4113:PrinterP…ngErrors.jpg] ( Version 6.68 )
[attachment=4114:PrinterP…ersion_7.jpg] ( Version 7.04 )
QUOTE (Support @ Aug 6 2010, 08:16 AM) <{POST_SNAPBACK}>I can't reproduce it..
I tested some more. It happens if adding an internal skin is the only change you make to the form containing the skin manager. The form is not recompiled then, so at run-time the skin is not present.
For reasons, I do not comprehend yet, it may eventually also disappear from the dfm file. I'm sure, if you assure the dfm is recompiled, the problem will go away.
I found out that clearing all SkinningRules makes skinning the Printer Properties dialog go away. But that's too rigorous. I want standard warnings, etc. to stay skinned.
QUOTE (Support @ Aug 2 2010, 03:59 PM) <{POST_SNAPBACK}>Hello
You can't add a skin? Or added skin is not visible later?
You can add the skin, but after closing the dialog, the skin is gone again.QUOTE (Support @ Jul 19 2010, 03:42 PM) <{POST_SNAPBACK}>Look on the attached project.
Part of button, which is under bevel, is not accessible. You have other result? %)
You're absolutely right
Sorry, but I meant BringToFront for buttons.
And I have checked this situation with standard controls before posting too.Step 1. Place TSpeedButton on form
Step 2. Place TBevel over this button
Button will not be accessible in the design-time, even while TBevel is placed over him. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />That's true. But run that application. Now you can select and click the button!
Well, at least in my system I can. <img src="style_emoticons//wacko.gif” style=”vertical-align:middle” emoid=”:wacko:” border=”0″ alt=”wacko.gif” />
QUOTE (Support @ Jul 19 2010, 03:04 PM) <{POST_SNAPBACK}>It's not a bug, you have placed the Bevel over buttons.” border=”0″ alt=”smile.gif” /><br />You must change z-order of these controls (BringToFront for buttons).<!--QuoteEnd--></div>
<p><!--QuoteEEnd--><br /><!--sizeo:2--><span style=)
Bevels should get a lower z-order than the components they enclose automatically. Try it: you'll see that with standard components it's impossible to get them in the wrong z-order. Even if you say Bring To Front for a TBevel, it will still go below the enclosing components.
At least, that's what I experienced
Posts
