It should be under Eudora71\QCSSL. Did you take a peek at my brain dump? It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's leaving. I replied with a link to my Org chart, at least so he can see that we're not as uncoördinated as we appear at first glance. Here's hoping he changes his mind, we need more people that are good with MFC. Especially now that we've made quite a bit on Kickstarter. I don't want this project to die—we seem to have everything but people!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now that I have you here... I've been meaning to ask.. When you people pull
the latest code from the repo you don't end up with an application that
compiles, so to say, "out of the box" do you? Sometimes you talk as if
that's the case, but I get like 100 errors and just as many, or more,
warnings.
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump?
It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's
leaving. I replied with a link to my Org chart, at least so he can see that
we're not as uncoördinated as we appear at first glance. Here's hoping he
changes his mind, we need more people that are good with MFC. Especially
now that we've made quite a bit on Kickstarter. I don't want this project
to die—we seem to have everything but people!
Not even close. Maclean got QCSSL to compile without warnings, I usually
don't even try to compile the C++ code (I make my changes and upload them
just like that, but it's usually removing extraneous logic, that sort of
stuff—like the trialware dialogue boxes and so on). If I compile anything,
it's usually the Help files, and those are on a different project
altogether.
Oh, that reminds me, I should put together a guide on MS Help.
One more thing. Would you be willing to help make the spellchecker work?
I've actually got a little bit of Sentry documentation and, as far as I
can understand, it should be possible to convert the Sentry API calls to
the nearest Nuspell equivalent. I will also try to get my hands on an
evaluation version of Wintergreen Sentry so that we have the manual and
everything.
Now that I have you here... I've been meaning to ask.. When you people pull
the latest code from the repo you don't end up with an application that
compiles, so to say, "out of the box" do you? Sometimes you talk as if
that's the case, but I get like 100 errors and just as many, or more,
warnings.
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump?
It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's
leaving. I replied with a link to my Org chart, at least so he can see that
we're not as uncoördinated as we appear at first glance. Here's hoping he
changes his mind, we need more people that are good with MFC. Especially
now that we've made quite a bit on Kickstarter. I don't want this project
to die—we seem to have everything but people!
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
I'm willing to help anywhere I can. What I would really like to do though,
is to start eliminating errors getting as close to compilable as I can get.
There are some pretty obvious stupid errors in there. Non-existent
includes, syntax errors, stuff like that.
I'd really like to go to war on those.
I'm aware I'm supposed to be the resident MFC "expert", which is maybe
stretching it a little to be brutally honest. Yes I have professional
experience with MFC but "expert"?
Where I worked, Maersk Data Denmark, which is now IBM, for about 7 years, I
was nicknamed "The fire extinguisher" (it rolls off the tounge a little
better in Danish :) alluding to my broad and varied skill set.
Don't worry though. I will take care of MFC
But that doesn't mean I can't contribute elsewhere.
Not even close. Maclean got SL to compile without warnings, I usually
don't even try to compile the C++ code (I make my changes and upload
them
just like that, but it's usually ibibib:8 extraneous logic, that sort of
stuff—like the trialware dialogue boxes and so on). If I compile anything,
it's usually the Help files, and those are on a different project
altogether.
Oh, that reminds me, I should put together a guide on MS Help.
One more thing. Would you be willing to help make the spellchecker work?
I've actually got a little bit of Sentry documentation and, as far as I
can understand, it should be possible to convert the Sentry API calls to
the nearest Nuspell equivalent. I will also try to get my hands on an
evaluation version of Wintergreen Sentry so that we have the manual and
everything.
On Sat, 8 Sep 2018 at 10:12, Soren Bro sbrothy@users.sourceforge.net
wrote:
Yes. I couldn't help but notice the fallout.
But yeh, let's hope he changes his mind.
Now that I have you here... I've been meaning to ask.. When you people pull
the latest code from the repo you don't end up with an application that
compiles, so to say, "out of the box" do you? Sometimes you talk as if
that's the case, but I get like 100 errors and just as many, or more,
warnings.
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump?
It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's
leaving. I replied with a link to my Org chart, at least so he can see that
we're not as uncoördinated as we appear at first glance. Here's hoping he
changes his mind, we need more people that are good with MFC. Especially
now that we've made quite a bit on Kickstarter. I don't want this project
to die—we seem to have everything but people!
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
I foresee, or rather as far as I've come, I can see that the errors begin
to be about a missing enum member called QUAL_EUDORA... or something. This
missing enum is obviously a member of some bit-shifting scheme.
Now, all programmers probably have their favourite way of doing this. That
is, if they're not forced to use HRESULT.
Does documentation exist for this scheme? I seem to remember it looked a
little weird but, perhaps I'm just rusty and the solution is staring me
right I'm the face.
Not even close. Maclean got QCSSL to compile without warnings, I usually
don't even try to compile the C++ code (I make my changes and upload
them
just like that, but it's usually removing extraneous logic, that sort of
stuff—like the trialware dialogue boxes and so on). If I compile anything,
it's usually the Help files, and those are on a different project
altogether.
Oh, that reminds me, I should put together a guide on MS Help.
One more thing. Would you be willing to help make the spellchecker work?
I've actually got a little bit of Sentry documentation and, as far as I
can understand, it should be possible to convert the Sentry API calls to
the nearest Nuspell equivalent. I will also try to get my hands on an
evaluation version of Wintergreen Sentry so that we have the manual and
everything.
On Sat, 8 Sep 2018 at 10:12, Soren Bro sbrothy@users.sourceforge.net
wrote:
Yes. I couldn't help but notice the fallout.
But yeh, let's hope he changes his mind.
Now that I have you here... I've been meaning to ask.. When you people pull
the latest code from the repo you don't end up with an application that
compiles, so to say, "out of the box" do you? Sometimes you talk as if
that's the case, but I get like 100 errors and just as many, or more,
warnings.
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump?
It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's
leaving. I replied with a link to my Org chart, at least so he can see that
we're not as uncoördinated as we appear at first glance. Here's hoping he
changes his mind, we need more people that are good with MFC. Especially
now that we've made quite a bit on Kickstarter. I don't want this project
to die—we seem to have everything but people!
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump?
It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's
leaving. I replied with a link to my Org chart, at least so he can see that
we're not as uncoördinated as we appear at first glance. Here's hoping he
changes his mind, we need more people that are good with MFC. Especially
now that we've made quite a bit on Kickstarter. I don't want this project
to die—we seem to have everything but people!
Pete almost didn't (Still not sure he does :) believe me when I said that I
don't get this project when I pull the code from the repo.
But the fact is that I don't.
I'm gonna try again when I get home, but I see no reason why this issue
should've fixed itself.
Why this project, and where is it?
Regards
--
Søren Bro Thygesen
It should be under Eudora71\QCSSL. Did you take a peek at my brain dump? It seems Mike Blazczak didn't get ANY of our eMails, and he wrote that he's leaving. I replied with a link to my Org chart, at least so he can see that we're not as uncoördinated as we appear at first glance. Here's hoping he changes his mind, we need more people that are good with MFC. Especially now that we've made quite a bit on Kickstarter. I don't want this project to die—we seem to have everything but people!
Yes. I couldn't help but notice the fallout.
But yeh, let's hope he changes his mind.
Now that I have you here... I've been meaning to ask.. When you people pull
the latest code from the repo you don't end up with an application that
compiles, so to say, "out of the box" do you? Sometimes you talk as if
that's the case, but I get like 100 errors and just as many, or more,
warnings.
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
Not even close. Maclean got QCSSL to compile without warnings, I usually
don't even try to compile the C++ code (I make my changes and upload them
just like that, but it's usually removing extraneous logic, that sort of
stuff—like the trialware dialogue boxes and so on). If I compile anything,
it's usually the Help files, and those are on a different project
altogether.
Oh, that reminds me, I should put together a guide on MS Help.
One more thing. Would you be willing to help make the spellchecker work?
I've actually got a little bit of Sentry documentation and, as far as I
can understand, it should be possible to convert the Sentry API calls to
the nearest Nuspell equivalent. I will also try to get my hands on an
evaluation version of Wintergreen Sentry so that we have the manual and
everything.
On Sat, 8 Sep 2018 at 10:12, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
I'm willing to help anywhere I can. What I would really like to do though,
is to start eliminating errors getting as close to compilable as I can get.
There are some pretty obvious stupid errors in there. Non-existent
includes, syntax errors, stuff like that.
I'd really like to go to war on those.
I'm aware I'm supposed to be the resident MFC "expert", which is maybe
stretching it a little to be brutally honest. Yes I have professional
experience with MFC but "expert"?
Where I worked, Maersk Data Denmark, which is now IBM, for about 7 years, I
was nicknamed "The fire extinguisher" (it rolls off the tounge a little
better in Danish :) alluding to my broad and varied skill set.
Don't worry though. I will take care of MFC
But that doesn't mean I can't contribute elsewhere.
Regards
) ö ö z
On Saturday, September 8, Ted Matavka /l/pkomnmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
I foresee, or rather as far as I've come, I can see that the errors begin
to be about a missing enum member called QUAL_EUDORA... or something. This
missing enum is obviously a member of some bit-shifting scheme.
Now, all programmers probably have their favourite way of doing this. That
is, if they're not forced to use HRESULT.
Does documentation exist for this scheme? I seem to remember it looked a
little weird but, perhaps I'm just rusty and the solution is staring me
right I'm the face.
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
I'm just thinking out loud on my cell phone in town. I'll learn more when I
get home.
I would love to be able to tell people I'm AFK.
Unfortunately, I can't always change the title.... Or can I?
Regards
--
Søren Bro Thygesen
Ironically, this missing-code issue did in fact resolve itself. There's
just no VS project file. The code is there.
Again, something I would probably have seen right away on Linux, where I
use the terminal for almost everything. :)
Regards
On Saturday, September 8, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen