Hi Luk, Thanks for reporting those problems. In the future, can you please use the fpGUI newsgroups to report fpGUI bugs. After all this is a Lazarus mailing list. ;-) See my signature for details of the fpGUI website where you will find information about the newsgroups. I have a web interface as well, if your are stuck behind a corporate firewall.
> 1) > The line > Include(ComponentState, csLoading); > didn't compile, but it was indicated that it only works in fpc 2.2.0 or > previous versions. I unknowingly exploited a bug in FPC 2.2.0 and earlier. This bug has been fixed (and a alternative method created but not used yet) in FPC trunk which is what you detected. At this moment I don't support FPC trunk - it's to early in it's development and to many things can change. I'll start supporting FPC trunk just before the next FPC release to make sure fpGUI will be supported when FPC is released. > SetBackgroundColor default clWindowBackground; > in gui_form gives error: Range check errors while evaluating constants. > The definition of the constant is: > clWindowBackground = $80000001; I have not detected this error in FPC 2.2.0 and FPC 2.0.4. Can you post your compiler parameters you are using. I'll enable range checking on my side to see what it does. > remark: I compile the gfx_package, and he tries to compile the gui_form, which > is included in gui_package ? Strange interdependencies... I do know about that (and don't like it either). The problem is I still can't figure out a way around that as it's required for modal form handling. I'm considering merging the two packages (gfx and gui) as I consider fpGUI as a whole, one thing. You are not going to create any other applications but GUI applications using fpGUI. The merge is still undecided though. > In the method TWideStringList.ExchangeItems, > "Illegal type conversion: Widestring to longint" for the line > Temp := integer(Item1^.FString); > and the following lines. > > All this happened on a Suse 86x64 machine, with a FPC 2.3.1 compiler from 21 > december 2007. Oops, gfx_strings.pas is not supposed to be part of the fpgfx_package. I'll remove it. It's a experimental unit not being used by anything. Hence the comment in the header... "PLEASE DO NOT USE THIS UNIT!!!!" :-) Umm, I see you are using a 64bit machine.... I don't have one to test on. If you have the time, would you mind trying fpGUI using FPC 2.2.0 (64bit version) and let me know how things go? Also as I mentioned in the beginning.... The lazarus mailing list has been very lenient by allowing so many fpGUI posts (I thank them, but don't want to push my luck). So could you possibly move all future fpGUI related messages to the newsgroup. Many thanks. Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
