Hi,
MSEide+MSEgui rev. 2.2beta2 for FPC 2.2.4 and 2.4 has been released:
http://sourceforge.net/projects/mseide-msegui/files/
There is an experimental x84_64_linux version too.
Questions and bug reports please to NNTP:
news://news.grid-sky.com/public.mseide-msegui.talk
Martin
_
On Friday 20 November 2009 21:24:17 Jorge Aldo G. de F. Junior wrote:
> arent there a /dev/something device for pcspeaker ?
With X11 one can use xbell().
Martin
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mai
On 20 Nov 2009, at 23:49, Bruce Bauman wrote:
> I need to convert the st_time field of the record returned by BaseUnix.FpStat
> to the year, month, day, hour, minute and second and need to compensate for
> the local timezone.
The dateutils unit contains the following functions that you can use
I need to convert the st_time field of the record returned by BaseUnix.FpStat
to the year, month, day, hour, minute and second and need to compensate for the
local timezone.
I've read over the RTL documentation and am thoroughly confused. Some of the
documentation of the interfaces say that th
arent there a /dev/something device for pcspeaker ?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
That's the idea of hints. Telling you you need to look at the code once,
and if it's ok => good. But if the hint was correct => fix it.
But if you later change your code it may become not ok again. I don't think
that this is good working practice. I would prefer to have the compiler
recognize
In our previous episode, Bruce Bauman said:
> I'm porting some code which called "system". Is there an equivalent under
> FPC, or do I need to use FpFork/FpExecV?
unix.fpsystem both with short annd ansistring arguments.
___
fpc-pascal maillist - fpc-p
I'm porting some code which called "system". Is there an equivalent under FPC,
or do I need to use FpFork/FpExecV?
-- Bruce
CONFIDENTIALITY NOTICE: This e-mail is confidential and intended
solely for the use of the individual or entity to which it is addressed. If
you are not the intended recip
In our previous episode, Graeme Geldenhuys said:
> Possible alternatives:
> Maybe under Linux the system.beep() can make a sound if stdout is
> available, otherwise write the word "beep" to the console (like the old
> silent movies did on screen), or flash the Scroll Lock keyboard light. :-)
Sure.
On Fri, 20 Nov 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt wrote:
No, the application can (for instance almost all daemons do) close
stdout. Programs that use ncurses will also be messed-up.
Ah, ok.
For CGI programs, stdout is also reserved for the HTML output.
Imagine someone el
Michael Van Canneyt wrote:
>
> No, the application can (for instance almost all daemons do) close
> stdout. Programs that use ncurses will also be messed-up.
Ah, ok.
> For CGI programs, stdout is also reserved for the HTML output.
> Imagine someone else's code doing a beep, and it ends up in y
Hello Graeme,
Friday, November 20, 2009, 9:42:16 AM, you wrote:
GG> I created a local dcpFillChar() which uses a out parameter. Inside the
GG> implementation of dcpFillChar() I enabled {$HINTS OFF}, and then called
GG> FPC's FillChar().
I had not tested it but you can create a general "Initializ
On Fri, 20 Nov 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt wrote:
No, because you don't know if a terminal is available or whether
standard output is writable.
As far as I know stdout is always available for Linux. Even if I compile
applications for X11 and launch them from a deskto
In our previous episode, Graeme Geldenhuys said:
> > No, because you don't know if a terminal is available or whether
> > standard output is writable.
>
> As far as I know stdout is always available for Linux. Even if I compile
> applications for X11 and launch them from a desktop icon, I can do
>
Michael Van Canneyt wrote:
>
> No, because you don't know if a terminal is available or whether
> standard output is writable.
As far as I know stdout is always available for Linux. Even if I compile
applications for X11 and launch them from a desktop icon, I can do
writeln() calls without proble
Am Friday 20 November 2009 09:42:16 schrieb Graeme Geldenhuys:
> Either way, my code is working now and is hint free.
I thought it is impossible, but you give me hope...
Rainer
>
>
> Regards,
> - Graeme -
___
fpc-pascal maillist - fpc-pascal@lists.f
Vincent Snijders wrote:
>
> For you as Lazarus user there is another option: Compiler options ->
> Verbosity -> uncheck Show hints for parameter "Sender" not used
Thanks Vincent, I did not know about this option. I guess it's type I
work my way through all the dialogs in Lazarus IDE to see what i
2009/11/20 Holger Bruns :
> Jonas Maebe schrieb:
>>
>> On 19 Nov 2009, at 14:30, Holger Bruns wrote:
>>
>>> Since iopl is still not available to fpc in its 64-bit-version, I should
>>> move to c for future port programming.
>>
>> $ man iopl
>> ...
>> This call is mostly for the i386 architectu
Graeme Geldenhuys schreef:
Another very annoying hint! :-) Solution - apply yet more workarounds.
FPC sure is verbal!
It is Friday again: To show that you are looking for problems with more than enough
solutions ...
Option #1:
--
procedure TForm.FormCreate(Sender: TObject);
b
On 20 Nov 2009, at 11:51, Michael Van Canneyt wrote:
No, because you don't know if a terminal is available or whether
standard
output is writable.
And I guess that if the crt unit is used, it would just put some
strange character on the screen.
Jonas
___
On Thu, 19 Nov 2009, Graeme Geldenhuys wrote:
Bruce Bauman wrote:
I'm porting some code which "beeps" the console. When I use
sysutils.beep() it doesn't work under Linux.
Looking at it's implementation in FPC 2.4.0-rc1 (Linux) I can indeed see
why it doesn't beep. :-)
-
Jonas Maebe schrieb:
On 19 Nov 2009, at 14:30, Holger Bruns wrote:
Since iopl is still not available to fpc in its 64-bit-version, I
should move to c for future port programming.
$ man iopl
...
This call is mostly for the i386 architecture. On many other
architec-
tures it doe
Martin wrote:
>
> If you use events you can not remove the parameters from your procedure
> declarations, so you get that hint...; Not that it bothers me, but if
> you got an easy solution...
Another very annoying hint! :-) Solution - apply yet more workarounds.
FPC sure is verbal!
Option #1:
Graeme Geldenhuys wrote:
Rainer Stratmann wrote:
But how do you solve the hints where a variable is initialised by a
function call with a var in the parameters then?
:-) That the exact problem I have and the reason for this message thread.
So I have a solution, but I consider
Rainer Stratmann wrote:
>
> But how do you solve the hints where a variable is initialised by a
> function call with a var in the parameters then?
:-) That the exact problem I have and the reason for this message thread.
In the due, I had to create a local work-around due to the fact that FPC
de
25 matches
Mail list logo
