C / C++ / MFC

copy paste linux style in windows

30-Oct-05 14:38

What grid control ?

Christian Graus - Microsoft MVP - C++

Noam Ben Haim30-Oct-05 4:50

Noam Ben Haim

30-Oct-05 4:50

does anyone here ever seen a linux-style copy-paste function for windows (I would assume it will be a shell extension)?
I mean, copy by marking (whatever you mark goes into the clipboard) and paste with the middle button.

Best
Noam

Noam Ben Haim
Project Leader
MobilEye
noam.benhaim@mobileye.com

Re: copy paste linux style in windows

__yb31-Oct-05 21:40

__yb

31-Oct-05 21:40

Nope. But it can be implemented in an app or even system wide.
Regards,
Yakov

help! how to carry out this function?

ewighell30-Oct-05 4:30

30-Oct-05 4:30

I created a List Control(CListCtrl) with Report type, and I created two columns for it.

I've been able to have the List Control display my data looked up from a database.

and now I want to modify the data in the List Control and write back to the database, is it possible to do this with List Control? if not, what should I do?

by the way, generally I want to keep the look of the report-type List Control.

any info is appreciated!

-------------------
I am learning C++ and English

Christian Graus30-Oct-05 11:40

30-Oct-05 11:40

The list control can neither read from or write to your database. But in the same way that you've looked up data and displayed it, so long as you're retrieving the primary key for records in the database, there's no reason you can't write back changes.

Christian Graus - Microsoft MVP - C++

ewighell30-Oct-05 14:35

30-Oct-05 14:35

I retrieve the record in the database with a CDaoRecordSet object.
of course I write back data with this CDaoRecordSet , too, but it seems that the data in the List Control can not be changed by the user, this is the problem .

besides,is CDaoRecordView an alternative?

-------------------
I am learning C++ and English

Christian Graus30-Oct-05 14:38

30-Oct-05 14:38

Oh, I see. You need the MSFlexGrid, or Chris Maunders grid control ( on this site ). They give you a more flexible control than the listControl.

Christian Graus - Microsoft MVP - C++

ewighell30-Oct-05 15:10

30-Oct-05 15:10

I just want to carry out the exact control which is demonstrated in the picture:
http://img168.photo.163.com/hu_yongliang/4822723/477599149.jpg
is MSFlexGrid the right choice?
-------------------
I am learning C++ and English

Christian Graus30-Oct-05 15:11

30-Oct-05 15:11

I don't have permission to access that image.

I believe that either a list control or a list view allows editing, but you need to write a bit of code to make it work. You should check out the C++ controls section of the site.

Christian Graus - Microsoft MVP - C++

ewighell30-Oct-05 15:18

Speed up compilation by ramdisk?

30-Oct-05 15:18

I see ,thank you so much all your help

-------------------
I am learning C++ and English

Christof Schardt30-Oct-05 0:46

Christof Schardt

30-Oct-05 0:46

Hello,

in good old Atari-days I used to love my ramdisk. On PC this doesn't seem to be a serious topic (I wonder why).

Compilation-time is the dominant bottleneck for most C++-programmers. So, in times of GB-Ram: why not use a ramdisk to reduce the heavy amount of harddisk-access?

Has anyone experience in setting up such an environment?
(which ramdisk? how large? what moved to the ramdisk: the temp-dir? the PCH? the whole project-files? how to setup this in VC++ ?
expected speed-gain?)

Thanks
Christof

Gary R. Wheeler31-Oct-05 3:26

Gary R. Wheeler

31-Oct-05 3:26

Christof Schardt wrote:
On PC this doesn't seem to be a serious topic

The current generation of PC's and Windows has overall better performance when any 'extra' available RAM is left to the operating system. Windows uses a portion of free RAM as a disk cache (there's the RAM disk you wondered about). The advantage today is that the O/S manages it for you, and you don't have to worry about copying files back and forth.

There are a number of things you can do to improve build performance. Make sure that any header files that don't change a lot are included in your precompiled headers. Break your projects into smaller pieces that are linked into the final application as object libraries (.LIB's), or even at runtime as DLL's. Your objective here is to reduce the amount of code that gets recompiled when you make changes, rather than to decrease the overall compile time itself. Most of the time, you are working on a small portion of the code, and don't need to recompile the whole thing.

Software Zen: delete this;

Blake Miller31-Oct-05 4:01

Blake Miller

31-Oct-05 4:01

You can also try to use the

#pragma once

in your header fils so they are not parsed multiple times, even if included multiple times.

I also find that keeping my HD defragmented helps a lot too.

If you run a virus scanner with 'on access' scanning, disable the folders containing your source files.

Disable some output options you might not use, such as class browser (I don't use it, speeds up build times since not making the BSC file for each project).

Christof Schardt31-Oct-05 5:21

Christof Schardt

31-Oct-05 5:21

Of course I have an include-guard in all my headers.
BTW:
Is there a difference between

<br />
#pragma once<br />
... // my code<br />

and

<br />
#ifnded XY_INCLUDED<br />
#define XY_INCLUDED<br />
... // my code<br />
#endif<br />

or is it just a MS-shorthand for this?

Thanks anyway for your additional hints.
Christof

Blake Miller31-Oct-05 5:54

Blake Miller

31-Oct-05 5:54

I do not know for certain.

It is my suspicion that the #pragma once will cause the file to be added to a table that it has already been processed, whereas the #ifndef does not necessarily preclude reparsing of the entire header, as one does not necessarily include or preclude the entire file within the confines of an #ifndef/#endif set.

The #pragma once, however, seems to imply, "hey, once you read this file for this compilation unit, don't bother reading it again". I favor adding the #pragma once if I now a header would never require reparsing within a single compilation unit. I prefer to create headers that do not depend upon such reparsing activity.