C / C++ / MFC

Member 1410515513-Jan-20 15:51

Member 14105155

13-Jan-20 15:51

Sure. I do not need this option- it was intended to demonstrate how my prog works to another users. And they do no not like (and for a reason) when some soft wants administrative privileges.

Richard MacCutchan13-Jan-20 22:35

Richard MacCutchan

13-Jan-20 22:35

Member 14105155 wrote:
And they do no not like (and for a reason) when some soft wants administrative privileges.

Well they are going to have to get used to it. Windows 10 (7 is out of support in a few days) uses this extensively in order to protect the users' systems from malicious software.

Member 1410515514-Jan-20 0:34

Member 14105155

14-Jan-20 0:34

Well, this is the reason to write soft that works without such privileges.

Richard MacCutchan14-Jan-20 0:47

Richard MacCutchan

14-Jan-20 0:47

You do not have a choice. The operating system sets the rules, and your software must work within those rules.

Member 1410515514-Jan-20 16:43

Member 14105155

14-Jan-20 16:43

I do have. A program can ask a user if he let it run with privileges, but users dislike such soft. Therefore, the choice exists, but it is very poor one.

Richard MacCutchan14-Jan-20 21:40

Richard MacCutchan

14-Jan-20 21:40

Member 14105155 wrote:
Therefore, the choice exists, but it is very poor one.

On the contrary it is a very good one, as it allows the user to control which programs are allowed to make significant changes to their system.

IsFileReady

Erich Ruth12-Jan-20 13:34

Erich Ruth

12-Jan-20 13:34

I use this code:

Quote:
BOOL C1095C::IsFileReady(CString path)
{
HANDLE hFile = CreateFile(path.GetBuffer(), GENERIC_READ, FILE_SHARE_WRITE | FILE_SHARE_READ, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);

if (hFile == INVALID_HANDLE_VALUE)
{
return FALSE;
}
else
{
CloseHandle(hFile);
return TRUE;
}
}

while (!IsFileReady(output.GetBuffer()))
{
Sleep(1);
}

which waits for a file to be created and then once it is, it
proceeds to the next job. The problem is, this code doesnt seem to
work every time. Im nervous now in using it. I need to wait for a
file to be full created and sometimes it may take 5+ minutes. Once its
created, then I want to move onto the next step. How can I adjust this
code to make it work every time? Please any response any one can give me
will be great appreciated.

leon de boer12-Jan-20 14:52

leon de boer

12-Jan-20 14:52

Wait on the directory change notification
ReadDirectoryChangesW function (winbase.h) - Win32 apps | Microsoft Docs[^]

This might help
GitHub - LdB-ECM/FolderWatcher[^]

In vino veritas

Stefan_Lang12-Jan-20 23:21

Stefan_Lang

12-Jan-20 23:21

Is that Linux sleep() or Windows Sleep()? Or, more to the point, are you sleeping for 1 second, or 1 millisecond? If the latter, maybe you should try to increase the time to around 100ms: The Windows file system is not very fast, and might be hamstrung by constantly trying to open nonexistant files.

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

leon de boer12-Jan-20 23:52

leon de boer

12-Jan-20 23:52

It's clearly windows no such thing as CreateFile in linux and he already stated it can take 5min to open the file (I assume of a network drive) so 100ms is not going to change anything Smile | :)

In vino veritas

David Crow13-Jan-20 5:02

David Crow

13-Jan-20 5:02

In addition to Leon's suggestion, there's also FindFirstChangeNotification().

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

Daniel Pfeffer13-Jan-20 23:38

Daniel Pfeffer

13-Jan-20 23:38

If you are waiting for the file to be fully created (i.e. completely written), then this code won't work. At best, it will wait until the file is created (i.e. when the other task opens it for writing).

The problem may be broken into two steps:

Wait until the file is created (i.e. it appears in the directory)
Wait until the file is closed (i.e. the writing is completed)

Others have given you good ideas about how to wait for the file to be created. In order to wait for the file to be completely written, the best way would be for the other application to create another file AFTER it is done with the data file. For example:

Your application waits for the creation of DATA.DAT
Other application creates file DATA.DAT (your application detects the creation)
Other application writes into DATA.DATA (your application waits for the creation of FINISHED.DAT)
Other application closes DATA.DAT
Other application creates FINISHED.DAT (your application detects FINISHED.DAT, and knows that DATA.DAT is ready)

There are some other points to handle (e.g. what happens if DATA.DAT is created before your application starts waiting for it?), but this is the basic idea.

Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.

Joe Woodbury14-Jan-20 20:15

Joe Woodbury

14-Jan-20 20:15

IF you know that this will be on a local drive, an alternative is to create the file in a different directory and then move it to the target directory.

Veteran VS2008 users here? Ever lost your debug functions?

Daniel Pfeffer14-Jan-20 20:58

Daniel Pfeffer

14-Jan-20 20:58

Subject to the limitation you mentioned, that would work, too.

Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.

charlieg9-Jan-20 1:59

Re: Veteran VS2008 users here? Ever lost your debug functions?

9-Jan-20 1:59

Yes, I know VS2008 is old, but I have to use it for a development project.

Anyway, a couple of weeks ago, I installed some software from Intel that broke my VS2008. Nothing would compile, I could not set breakpoints, etc. Using a clean Windows 10 VM, I re-installed VS2008, SP1 and an ATL update required for WEC7 development. I can compile and set breakpoints again. Joy. Now it gets a little weird. The step over (F10) and step into (F11) functions refuse to work. They are being treated as the go (F5) commands, making it just about impossible to get anything done. Note that even the menu debug commands behave this way.

Now it gets a little weird now - it seems to be project/solution related. If I debug project A the functions work, debug Project B (the one I really need to work on) they don't.

So a clean re-install did not fix this, a reset to all settings didn't fix it, deleting .suo, etc files didn't fix it... maddening OMG | :OMG:

Thoughts? Ever run into this?

Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...

"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759

Afzaal Ahmad Zeeshan9-Jan-20 22:28

Afzaal Ahmad Zeeshan

9-Jan-20 22:28

Perhaps some project-specific configurations are overriding the behavior?

Check this thread, asp.net - 'Step Into' not working in Visual Studio? - Stack Overflow

The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~

Re: Veteran VS2008 users here? Ever lost your debug functions?

charlieg10-Jan-20 3:51

Re: Veteran VS2008 users here? Ever lost your debug functions?

10-Jan-20 3:51

You would think, but depending on machine / project the behavior varies.

phil.o9-Jan-20 22:46

phil.o

9-Jan-20 22:46

It's a long shot, but if the issue is project-specific, then you can try to delete the .suo file from the project directory and re-open the project.

"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."

Re: Veteran VS2008 users here? Ever lost your debug functions?

charlieg10-Jan-20 3:53

Re: Veteran VS2008 users here? Ever lost your debug functions?

10-Jan-20 3:53

This is a common suggestion - I've done it several times on multiple projects with no success.

The part that I don't get is that the actual menu functions don't work, implying some sort of corruption in VS2008 - *but* that makes no sense since one project will work and the other won't. It should be corrupt for both.

_Flaviu9-Jan-20 23:19

_Flaviu

9-Jan-20 23:19

Another approach is to create a VS2008 valid project and to import all your files from the old one. Then you will have your app settings fresh new. I know, is a little work to do, but I am sure will solve your issue.

modified 10-Jan-20 5:46am.

Re: Veteran VS2008 users here? Ever lost your debug functions?

charlieg10-Jan-20 3:58

Re: Veteran VS2008 users here? Ever lost your debug functions?

10-Jan-20 3:58

Good suggestion, but I cannot even get a simple Yellow World dialog app to debug properly.

Maddening.

Thanks for the suggestions

charlieg10-Jan-20 4:15

Re: Veteran VS2008 users here? Ever lost your debug functions?

10-Jan-20 4:15

Well, I may have isolated the issue a little closer - the behavior changes depending on what SDK I select - I have multiple embedded CE projects.

charlieg21-Jan-20 11:53