Recent

Recent Posts

Pages: [1] 2 3 ... 10
1
General / Re: How can i make this window ?
« Last post by Handoko on Today at 06:23:43 pm »
It is relatively easy to write a custom popup, for example this is my Frameless popup in the User Interface section in the link below:

https://wiki.freepascal.org/Portal:HowTo_Demos#User_Interface
2
LCL / Re: Form scaling
« Last post by wp on Today at 06:22:43 pm »
I don't know how CodeTyphon handles form scaling. Maybe it is not compatible to the way Lazarus does it. Is the box "Use LCL Scaling" checked after opening the project in Lazarus? In Windows, you should also make sure that "Use manifest resource" is checked and one of the "on" options in the "DPI awareness" combobox is selected.

But in general: I don't think that it is a good idea to switch between Codetyphon and Lazarus. Either use CodeTyphon, then stay with it. Or use Lazarus, then stay with it, too.
3
Cocoa / Re: CocoaInt.CocoaIconUse no longer recognized?
« Last post by dsiders on Today at 06:22:10 pm »
Code: Pascal  [Select][+][-]
  1. CocoaInt.CocoaIconUse := True;
now gives error
Quote
Idenfier not found CocoaIconUse
Has this been deprecated since removed? (Using recent stable build as downloaded by FPCUpDeluxe)

In Lazarus trunk, it is located in lcl/interfaces/cocoa/cocoaconfig.pas not cocoaint.pas.
4
LCL / Form scaling
« Last post by fxeconomist on Today at 06:11:14 pm »
Hi,

I noticed that as I worked on my project in CodeTyphon at home on my FullHD monitor, there was practically no change when I moved the project on my other computer with UHD resolution.

However, after I migrated the project to Lazarus, I noticed the form Width and Height are in pixels, and the form did not scale.
Is there any property to restore this scaling feature ?
5
Good question. If you insist on including binutils in the flow one thing that seems to work on both new and older versions is to always use gas and ld:
Code: [Select]
fpc -XPx86_64-w64-mingw32- -Aas -n -O4 -Si -Sc -Sg -Xd -CX -XXs -Px86_64 -Rintel -Twin64 -Us system.pas
fpc -XPx86_64-w64-mingw32- -Aas -n -O4 -Si -Sc -Sg -Xd -CX -XXs -Px86_64 -Rintel -Twin64 uefimain.pas
x86_64-w64-mingw32-ld --gc-sections --oformat pei-x86-64 uefimain.o uefi.o system.o -e efi_main -o MAIN.EFI

That works here with -Cg and -r as well:
Code: [Select]
fpc -XPx86_64-w64-mingw32- -Aas -n -O4 -Si -Sc -Sg -Xd -CX -XXs -Px86_64 -Rintel -Twin64 -Cg -Us system.pas
fpc -XPx86_64-w64-mingw32- -Aas -n -O4 -Si -Sc -Sg -Xd -CX -XXs -Px86_64 -Rintel -Twin64 -Cg uefimain.pas
x86_64-w64-mingw32-ld --gc-sections -r --oformat pei-x86-64 uefimain.o uefi.o system.o -e efi_main -o MAIN.EFI
6
I get the error with 0-bit reloc when trying to compile with -shared
When just using "x86_64-w64-mingw32-ld  --gc-sections --oformat pei-x86-64 uefimain.o uefi.o system.o -e efi_main -o MAIN.EFI link.lds" it works fine

Why does it need to be relocatable? As far as I can tell the Win64 code generates position independent code by default, but I'm not an expert on Windows stuff
When I execute the shell code that x86_64-w64-mingw32-ld --gc-sections --oformat pei-x86-64 uefimain.o uefi.o system.o -e efi_main -o main.efi -Tlinker.lds,I got the error that:
x86_64-w64-mingw32-ld: error: 0-bit reloc in dll
uefimain.o:uefimain.pas:(.pdata.n_uefimain_$$_efi_main$pointer$pefi_system_table+0x0): relocation truncated to fit: IMAGE_REL_AMD64_ADDR32NB against `.text.n_uefimain_$$_efi_main$pointer$pefi_system_table'
uefimain.o:uefimain.pas:(.pdata.n_uefimain_$$_efi_main$pointer$pefi_system_table+0x4): relocation truncated to fit: IMAGE_REL_AMD64_ADDR32NB against `.text.n_uefimain_$$_efi_main$pointer$pefi_system_table'
uefimain.o:uefimain.pas:(.pdata.n_uefimain_$$_efi_main$pointer$pefi_system_table+0x8): relocation truncated to fit: IMAGE_REL_AMD64_ADDR32NB against `.xdata.n_uefimain_$$_efi_main$pointer$pefi_system_table'
So how to do to solve these error above,buddy?
7
@VisualLab, CCRDude
Despite I like the enumerators too, they are IMHO just a syntax sugar and much underdeveloped.

Consider the following loop:
Code: Pascal  [Select][+][-]
  1.   for I := Pred(C.Count) downto 0 do
  2.     if SomeCond(C[I]) then
  3.       C.Delete(i);

8
General / Re: pre-processor symbol when FPC symbol is defined/used
« Last post by paule32 on Today at 05:11:35 pm »
Thank you. This works like a charm  ;D
9
Yes, I know that.
In that case sorry for being a redundant remark. I wasn't sure whether or not you did,

There is no reason to apologize. Everything is OK. This information can be used by someone else who doesn't know it and is browsing the forum.

But I believe this:

in Fpc and ObjFpc modes it should be disabled by default.
The way these kind of things work is usually a mystery to me. Might even be debatable what is the 'correct' way to do it but experience in the past have shown there always seem to be a (valid) reason for having chosen the approach as (currently) implemented.

Indeed, it may be so. Sometimes, after a longer period of time, certain shortcomings of the solution used may become apparent.
10
General / Re: How can i make this window ?
« Last post by TRon on Today at 05:06:35 pm »
On a windows machine IIRC the colors would be controlled by OS.
Oh, I hadn't thought of that one.

There seem to be system theme management going on inside a hintwindow (I do not know if it is active by default) so you might be right there.

In which case, 2 out of 3 is also not bad though I understand that is not what TS is looking for :-)

I rather wait with further suggestions until all specs are on the table... TS seem to have a habit of adding additional requirements as suggestions go along and I am not in the mood for these games with crystal balls right now.

AFAIK there is not a ready to go component/solution that does exactly as TS seem to want and I am currently trying to avoid suggesting to use a video playback component to literally provide what TS asks for  O:-)
Pages: [1] 2 3 ... 10

TinyPortal © 2005-2018