[QUOTE=swl551;327642]exactly :smile:[/QUOTE]

Look at my little gif image from a couple of posts back. Under the "WORKING" heading I see the current bit level 72-73, a vertical bar, a mysterious 3, then the exponent 61711537.

What is that 3 following the vertical bar?

[QUOTE=Chuck;327644]Look at my little gif image from a couple of posts back. Under the "WORKING" heading I see the current bit level 72-73, a vertical bar, a mysterious 3, then the exponent 61711537.

What is that 3 following the vertical bar?[/QUOTE]


3 is the max bit level for that assignment. so if it said 70-71|3 it mean you working the early stages from 70-71 where the max is 73. 72-73|73 would mean u on the final stage.

if you have stages=0 in mfaktc then you should turn this setting off in MISFIT's MISC configuration tab. However stages=1 is the default and the recommended setting for mfaktc

[QUOTE=swl551;327646]3 is the max bit level for that assignment. so if it said 70-71|3 it mean you working the early stages from 70-71 where the max is 73. 72-73|73 would mean u on the final stage.

if you have stages=0 in mfaktc then you should turn this setting off in MISFIT's MISC configuration tab. However stages=1 is the default and the recommended setting for mfaktc[/QUOTE]

Will the program create its MISFITWorktodo file on the first work fetch or should I make an empty one?

[QUOTE=Chuck;327647]Will the program create its MISFITWorktodo file on the first work fetch or should I make an empty one?[/QUOTE]

The program takes care of that.

[QUOTE=Chuck;327647]Will the program create its MISFITWorktodo file on the first work fetch or should I make an empty one?[/QUOTE]


click ADD WORK button then click the fetch button to forece an immediate fetch. that is best to confirm your configuration is correct. after that auto fetching will occur. Use the Work Calculator if you don't know what values to choose.

After MISFIT has been running minimized to the system tray, when I try to look at the program this window comes up. I cannot get the window to enlarge.

The program is fetching work, reporting the results, and sending me a status report via email. Everything is working EXCEPT I cannot get the window to enlarge to see what is going on.

[QUOTE=Chuck;327681]After MISFIT has been running minimized to the system tray, when I try to look at the program this window comes up. I cannot get the window to enlarge.

The program is fetching work, reporting the results, and sending me a status report via email. Everything is working EXCEPT I cannot get the window to enlarge to see what is going on.[/QUOTE]

Chuck, I found the cause of the window smashing. (If a form height calculation occurs while minimized the height of the form is totally incorrect afterwards) Solution: Don't calculate form size unless WindowState=Normal

However it is clear there are a lot more variables at play here than I anticipated and testing all UI scenarios will take a lot of time.

So you can do two things for now...

1. restart the app and don't minimize it.
2. download and assist in testing 2.4.1.1(test) version to help confirm I've addressed the [B]minimize[/B] issue. At this point I am not stating all the form size issues are addressed since there is a cascading effect here.

[QUOTE=swl551;327698]Chuck, I found the cause of the window smashing. (If a form height calculation occurs while minimized the height of the form is totally incorrect afterwards) Solution: Don't calculate form size unless WindowState=Normal

However it is clear there are a lot more variables at play here than I anticipated and testing all UI scenarios will take a lot of time.

So you can do two things for now...

1. restart the app and don't minimize it.
2. download and assist in testing 2.4.1.1(test) version to help confirm I've addressed the [B]minimize[/B] issue. At this point I am not stating all the form size issues are addressed since there is a cascading effect here.[/QUOTE]

I discovered that by repeatedly pressing F3, each press opens the window up a bit — about ten presses and it is almost back to normal size. Can't quite get the sixth button (below "Export results") exposed, but it is clickable.

If I download the new version, do I just need to unzip and replace the misfit.exe and everything else can stay the same? And can't you just allow the user to resize the window as desired?

[QUOTE=swl551;327646]3 is the max bit level for that assignment. so if it said 70-71|3 it mean you working the early stages from 70-71 where the max is 73. 72-73|73 would mean u on the final stage.[/QUOTE]

Another very cool feature! I had not really focused on that detail, and it is good to know the meaning. I take it that MISFIT only submits an assignment when all phases are done? Excellent if so! With manual submissions in earlier versions of mfaktc it could be confusing if a partial run was submitted, though GPU72 didn't count it as completed until the pledged level was fulfilled.
[insert many positive smileys here]

[QUOTE=kladner;327736]Another very cool feature! I had not really focused on that detail, and it is good to know the meaning. I take it that MISFIT only submits an assignment when all phases are done? Excellent if so! With manual submissions in earlier versions of mfaktc it could be confusing if a partial run was submitted, though GPU72 didn't count it as completed until the pledged level was fulfilled.
[insert many positive smileys here][/QUOTE]

MISFIT does not wait for all stages to be complete if STAGES=1. Set STAGES=0 to ensure only a single completed result is uploaded.

See mfaktX.ini for information on STAGES.

Thanks! :tu:

EDIT: I was aware of the Stages explanation in the .ini file, and Oliver also explained some time back why mfaktc 2.0 is more efficient with Stages=1. I'll have to track that down and re-read it. With previous versions I was in the habit of running Stages=0. But, as mentioned, GPU72 deals with partially done pledges just fine, so I'll stay with the more-efficient =1 setting. :smile: