--------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBC00008 Date: 07/07/96 From: TOMMY USHER Time: 07:46am \/To: PETER COLLIS (Read 3 times) Subj: Code going to waste PC>G'day All, PC>Over the last few months i've seen some great code examples from PC>people which when i find them interesting or a good example of PC>something i don't know i save them off to a FIDO directory under my PC>Delphi directory for later use. PC>This makes me ask "has anyone ever thought about starting a Delphi PC>snippets file" if there is one where would i find it, if not then how PC>about we start one. Well, there is SWAG, which now covers Delphi, but I can see where a Delphi specific archive would also have merit. --- * QMPro 1.52 * A clean room is a sure sign of a broken computer. --- WILDMAIL!/WC v4.12 * Origin: GC-BBS! (1:226/810.0) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBC00009 Date: 07/07/96 From: TOMMY USHER Time: 07:48am \/To: CHEW GHEE HONG (Read 3 times) Subj: Delphi ram requirements CGH> Currently I have a P-120 with 16 MB RAM. I was wondering whether I should CGH>upgrade my RAM to 32MB since you say the more RAM, the faster the CGH>performance. Do you think the added memory will be a worthwhile upgrade CGH>since RAM is so cheap at the moment? There is a certain law of diminishing returns at work here. Up to a point, more RAM increases speed. Going from 8 to 16 is dramatic. From 16 to 32, less dramatic. And from 32 to 64, even less so. Still, it can't hurt. --- * QMPro 1.52 * Honk if you love peace and quiet. --- WILDMAIL!/WC v4.12 * Origin: GC-BBS! (1:226/810.0) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBC00010 Date: 07/07/96 From: TOMMY USHER Time: 12:39pm \/To: BRYAN SMITH (Read 3 times) Subj: RUN A DOS BAT FILE. BS> TU> HOWEVER, if you need to get fancy, and have the calling BS> TU> program wait, there is a shareware component that will do this. BS>No need for shareware ... BS>WinExecAndWait was posted here by Viggo Poulsen on Nov. 23 '95. BS>--------------------------------------------------------------------- BS>function WinExecAndWait(Path : Pchar; Visibility : word) : word; BS>var BS> InstanceID : THandle; BS> Msg : TMSg; BS>begin BS> InstanceID := WinExec(Path,Visibility); BS> if InstanceID < 32 then { a value less than 32 indicates an Exec error } BS> WinExecAndWait := InstanceID BS> else BS> repeat BS> while PeekMessage(Msg,0,0,0,PM_REMOVE) do begin BS> if Msg.Message = WM_QUIT then BS> halt(Msg.wParam); BS> TranslateMessage(Msg); BS> DispatchMessage(Msg); BS> end; BS> until GetModuleUsage(InstanceID) = 0; BS>end; BS>--------------------------------------------------------------------- BS>Viggo should win a prize for the "most frequently-reposted code" :-) BS>You might want to wrap a shell around it that will accept a Pascal string BS>as the path argument. Or you can use the "@1" trick to fake a pChar ... BS>var s : string ; BS>s := 'BACKUP.BAT' ; s := s + #0 ; BS>dec(s[0]) ; { not needed if don't need to re-use s as a pascal string later BS>WinExecAndWait(@s[1],SW_SHOWMAXIMIZED) ; BS>MessageDlg('Backup complete, remove disk from A:',mtInformation,[mbOK],0) Okay, the question is, does this work for WIN32? I have used a similar routine under C/C++ for Window 3.1, but was under the impression that Windows 95 had eliminated some of the necessary elements of this routine. --- * QMPro 1.52 * "Oh, how absolutely typical of your species!" -- Q --- WILDMAIL!/WC v4.12 * Origin: GC-BBS! (1:226/810.0) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBD00000 Date: 07/08/96 From: BRYAN SMITH Time: 02:25pm \/To: DEREK BENNER (Read 4 times) Subj: XOR on Canvas.Pixels[] On 07 Jul 96 Derek Benner said to Bryan Smith... BS> It seems to behave as though what is being XOR'ed is not the clNavy BS> LongIntrepresentation of $007F0000 but rather a 4-bit "DOS text BS> foreground colour" BS> representation of clNavy as $1, where 1=blue, 2=green, 4=red, BS> 8=brightness.The NOT of $1 (dark blue) is $E, i.e. bright yellow, BS> which is what you in BS> fact see. DB> non-standard XOR values. If you assume that your sprites are limited DB> to 20 to 30 colors, this will probably bring that number down to 20-50 DB> logical palettes that will need to be initialyzed (This is a DB> guesstimate, NOT a rigorous analysis!) Would that work for an average DB> application? Probably. The "XOR value" is presumably determined by the colour of the text that you BitBlt with. If it is white text on black background, the background XOR with $0 does nothing, and the foreground presumably XOR's with the 4-bit colour white, or $F - that's the way it behaves. So I guess I can change the colour of the sprite by juggling the colour of the text that I blit with. Will try it out, thanks for your suggestion. I don't understand this palette stuff at all. I'm running 256 colour, but it often seems that I am still restricted to 16 colours, e.g. the screen main background may be one of 256, but the background colour for text written over that background seems to find the "nearest of 16" colour. --- PPoint 2.00 * Origin: Kingston, Canada (1:249/109.11) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBD00001 Date: 07/08/96 From: DON KRAUSE Time: 06:14pm \/To: DEREK BENNER (Read 4 times) Subj: Delphi ram requirements >than three months ago!?! When will this RAM madness end! Never, though I actually heard the sales geek on the home shopping network say "this system holds up to 128 megs of ram. You'll NEVER need more than that!" Sounds like 1980 all over again . =Don= --- * QMPro 1.52 * Drop your carrier ... we have you surrounded! --- InterEcho 1.18 * Origin: the Squirrel's Nest BBS (909) 338-4748 (1:207/501) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBD00002 Date: 07/04/96 From: NICOLA ROLANDO Time: 06:29pm \/To: LANGLEY MCKELVY (Read 4 times) Subj: DBMemo Fields Hi Langley, On , you wrote me: LM> Each line of data is accessible by its line number ie Memo1.Lines[1]. This is good for a Memo component, but I was talking about a Memo Field in a Database (a kind of Blob field). I cannot access it in this way, I think... I was only able to access data in a memo field using a TDBMemo _Component_, sometimes ,aking it invisible. But I don't think it's the best way to do ... Bye bye! Nicola --- * Origin: Beware of Quantum ducks (Quark!Quark!Quark!) (2:334/21.5) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBD00003 Date: 07/05/96 From: CURT TABOR Time: 03:58pm \/To: JORGEN DE GIER (Read 3 times) Subj: Delphi equiv for C To: Jorgen De Gier RE: Delphi equiv for C On 7/1/96, Jorgen De Gier offered the following words of wisdom to Mick Mcham about Delphi equiv for C >>A Borland spokesmen told me about a C version of Delphi. >>The major problem is that Borland doesn't own C++ as they >>do own Object-Pascal. >> What would need to be done to the language to support that kind of environment? Curt * QWKBACK * The first 256 bit QWK system for the Cray! * Work is for people who don't surf. --- Maximus/2 3.01 * Origin: Pebble BBS (1:202/1207) --------------- FIDO MESSAGE AREA==> TOPIC: 269 DELPHI Ref: DBD00004 Date: 07/07/96 From: CURT TABOR Time: 09:50am \/To: PETER COLLIS (Read 3 times) Subj: Adding Internal file inf To: Peter Collis RE: Adding Internal file info >>Does anyone know how to add file information to a Delphi EXE file?. >>The type of info i mean is the info you get by highlighting a Windows >>EXE or DLL in filemanager then clicking File->Properties. >> >> Pete. >> Email:pcollis@ozemail.com.au >> That's called Version Information and you can add it with Resource Workshop if you've got a copy. I believe that there is a version component on CSERVE but I don't know what it's called. Curt * QWKBACK * The first 256 bit QWK system for the Cray! * There is nothing that good day of surfing won't cure. --- Maximus/2 3.01 * Origin: Pebble BBS (1:202/1207)