Forum Replies Created
-
Posts
-
It did the trick.
actToolsScaleModeAuto.Caption := 'Auto (' + IntToStr(aScalePercents[smMain.SysFontScale]) + '%)';
Thank you very much.
No problem. Thanks.
Perhaps if I was testing this on a true 4K device it would look better. But with me using Windows 7 1920×1080 I imagine that squeezing 144 DPI (150%) might be stretching it some and causing some distortion.
1. No change when changing scaling mode as far as momentary portions of the window appearing white. Are you still looking into this or is it a dead issue?
2. Fixed. Thanks.
It is not working. I have an idea what is happening.
I built another project with an skin manager, skin provider, action list, skin image list, skin virtual image list and an image list.
I put 2 image in each image list. Added one action and set the image index to 0.
I then set the action list images to ImageList1. The image appears in the action list.
I then changes the action list images to sAlphaImageList1. The image does not appear in the action list. I tried the same with sVirtualImageList1. Same result.
I had been wondering why the image was not appearing beside the action. It use to if I remember right.
Could this be part or the whole problem I am observing?
I also add a non skin project that correctly changes the image from one to another at design time.
Sorry for the trouble. I have been using your components for 6 years and I appreciate you effort to expand their capabilities.
#4. I have more information.
When you place a label (alNone, but is far left and right alignment) over another label that is alClient, when you are in sm125 or sm150, the label seems to get shoved further right. Does that make sense? I solved this be putting both labels in a panel with one label alClient and the other label alRight.
I know that was probably bad placement,but I have always been able to get away with it. But these scaling modes is showing that some of my placements are pretty bad.
That is good to know. However, if you try to use TV-C using v10 controls you get this warning.
This version of the skin has not complete support by used AlphaControls package release.
Components must be updated to latest version for using this skin.
As a general rule, I move to the new version (v11 in this case) when it moves out of the beta phase. In the mean time I stick to the current version (v10).
The reason that I asked this question in the first place is because AlterMetro2016 was released after TV-C and it can be used with v10. See the possible confusion.
I must be missing something. I followed your instructions. The result is the right panel is still there and the splitter is gone. I did not do any resizing or visibility changes.
I am using 10.29.
I withdraw this. The jury is still out.
Again, I cannot duplicate this.
sSkinManager1.BeginUpdate;
sSkinManager1.Active := True;
sSkinManager1.EndUpdate;
If I comment out BeginUpdate and EndUpdate, no error is produced. It is still too early to confirm this.
I have an update. I was lucky that I did in fact find 10.26 and its skins. I uninstalled 10.27 and installed 10.26.
As I thought, 10.26 has no problem when trying to add a TsTrackbar to a project while 10.27 has an Access Violation when trying to add a TsTrackbar to a project.
One interesting thing I observed. When changing skins in 10.27 there was a lag in changing the skin (in other words it was not a smooth instant change). 10.26 is very smooth and very fast. In fact I consider 10.26 as a standard of excellence that I will use to compare future updates.
I await 10.28 and the fix for this problem.
Another thing. I kept referring this new version as 10.26. It is in fact 10.27. However, on your main page it is referred to as 10.26. Sorry for my confusion.
I am not going back to my previous messages and correct them. Just moving forward.
I just realized something. I am stuck with 10.26 because I do not have the zip file password for 10.25. Oh well.
Never mind about the download requests. I still have them. I am going back to 10.25 and I guess stay there until this issue is resolved.
I find it interesting as to why the runtime bpl would be issuing an access violation when you in the IDE and just opening one of the forms. The error also occurred when closing the form.
Your demo had several of the forms issue this error when opening them and it was the same error.
