MFC 23

CARD PRINCIPAL

Thales Leites (14-3) vs. Dean “The Boogeyman” Lister (11-6)
Jason “The Athlete” MacDonald (21-13) vs. “King” Solomon Hutcherson (11-5)
Bryan “The Beast” Baker (10-1) vs. Art “Pachuco” Santore (18-6)
Ryan “The Big Deal” Jimmo (11-1) vs. Emanuel “The Hardcore Kid” Newton (12-5-1)
Marvin “The Beastman” Eastman (16-11) vs. Dwayne Lewis (9-4)

CARD PRELIMINAR

Jesse Juarez (11-5) vs. Joe “Jitsu” Christopher (9-2)
Ryan “The Vanilla Gorilla” Fortin (5-1) vs. Nick “The Quiet Assassin” Penner (8-1).
Ryan Machan (9-3) vs. “Rajin” Kajan Johnson (16-10)

This essay covers:

• PreTranslateMessage and message interception mechanism
• Avoiding having the Enter and Escape keys terminate the dialog
• The WM_GETDLGCODE message

The interception mechanism in MFC is implemented through the magic of CWnd class virtual method PreTranslateMessage. When window receives the message, before actually handling it, it bubbles the message up through its parent and grandparents, all the way up to the topmost window, calling CWnd::PreTranslateMessage for each one. Something like this:


BOOL CWnd::PreTranslateMessage(MSG* pMsg)
{
for (pWnd = /* window that sent msg */; pWnd; pWnd=pWnd->getParent())
if (pWnd->PreTranslateMessage(pMsg))
return TRUE;

return FALSE; // not handled
}


PreTranslateMessage return value can be either TRUE, meaning that message were handled, or FALSE otherwise. If all the windows in the hierarchy will return FALSE in their PreTranslateMessage, the message will eventually be handled by the window that initialy received the message. But if one of the windows in the hierarchy returns TRUE the hall sequence breaks down and no other window, including the one that initiated the sequence, will have the chance to process the message. Thus allowing any of the parent windows to hijack the message.

By default CDialog is programmed to intercept some of its child controls messages. Two important of them concerning keyboard input are ENTER and ESC key strokes. The dialog handlers for these events are OnOk and OnCancel corespondingly. The default behaviour for both of these handlers is to close the dialog.

This default behaviour can sometimes be the cause of unwanted behaviour. For instance, lets say that your dialog has a number of text input fields that user should fill in. What you probably like to be is when the user finishes filling one input field and presses ENTER, the focus is switched to the next input field. But what you get is that the dialog will close upon the first time user hits the ENTER button.

There are a couple of ways to change the default behaviour. First one is simply to override the default handler s.t it will suite your needs. For instance, if you wish that your dialog will stay open despite ENTER key, just delete the body of OnOk method.


void MyDialog::OnOK()
{
// CDialog::OnOk();
}

Or you can even override PreTranslateMessage itself, like this:

BOOL MyDialog::PreTranslateMessage(MSG* pMsg)
{
if(pMsg->message==WM_KEYDOWN)
{
if(pMsg->wParam==VK_RETURN)
return TRUE; // the message shouldn't be dispatched any farther
}

return CDialog::PreTranslateMessage(pMsg); // default handler
}


The other way and in my opinion, the preferred one, is to give the responsibility for non-standard behaviour to the control itself. But since we want to implement non-standard behaviour we can’t use any of standard MFC controls and thus make a new control by ourselves. From first glance it seems odd, but if you think about it a bit, it’s perfectly logical and its much more natural than altering the default handlers or the message route.

If you want some new behaviour, it makes much more sence to create a new class that encapsulates it and not to impose non-standard behaviour on standard objects. The standard objects were designed to work certain way, don’t try to twist them around to impose on them un-natural behaviour. You want a new behavior- build a new class!

And actually it isn’t complicated at all. After all you don’t have to write new control from the scratch, it’s perfectly alright to derive it from standard MFC control – and this can be accomplished just with few clicks in VS. After your class is created, just override the WM_GETDLGCODE message handler like this:


UINT EnterEdit::OnGetDlgCode()
{
// ask dialog superclass not to handle keyboard input that intented for me
return CEdit::OnGetDlgCode() | DLGC_WANTALLKEYS;
}

The message about ENTER keystroke will still reach the parent dialog via interception mechanism, but now it will know not to handle it.

Have you ever face a situation to make an edit box that support only floating point numbers. That means the edit box do not accept more than one . (dot) and characters. How shall we do it? Just a trick!

First of all we have to a derive a new CEdit class to our project and make a control of that on our window. Then we need to put a handler for WM_CHAR and EN_UPDATE messages for our custom edit class. Within the WM_CAHR message handler we can backup the existing value and within the EN_UPDATE message handler we can check the modified value. If its a valid double value, then only we need to update this with the edit control otherwise we can keep the previous value.

MyEdit.h

class CMyEdit : public CEdit
{
   DECLARE_DYNAMIC(CMyEdit)
public:
   CMyEdit();
   virtual ~CMyEdit();
protected:
   DECLARE_MESSAGE_MAP()
   afx_msg void OnChar(UINT nChar, UINT nRepCnt, UINT nFlags);
   afx_msg void OnUpdate();
private:
   CString m_strPrevValue;
   int m_nLastSel;
};

MyEdit.cpp

CMyEdit::CMyEdit()
{
   m_nLastSel = 0;
}

CMyEdit::~CMyEdit()
{
}

BEGIN_MESSAGE_MAP(CMyEdit, CEdit)
   ON_WM_CHAR()
   ON_CONTROL_REFLECT(EN_UPDATE, OnUpdate)
END_MESSAGE_MAP()

void CMyEdit::OnChar(UINT nChar, UINT nRepCnt, UINT nFlags)
{
   GetWindowText(m_strPrevValue);
   m_nLastSel = GetSel();
   CEdit::OnChar(nChar, nRepCnt, nFlags);
}
void CMyEdit::OnUpdate()
{
   CString str;
   GetWindowText(str);
   errno = 0;
   LPTSTR endPtr;
   double doubleValue = _tcstod(str, &aEndPtr);
   if (*endPtr)
   {
      SetWindowText(m_strPrevValue);
      SetSel(m_nLastSel);
   }
}

If you want to allows only digits to be entered into the edit control just use the style ES_NUMBER.

JUBILE – JUBILEE ENTERPRISE PUBLIC COMPANY LIMITED
IPO価格2.80バーツで本日より取引開始。（10時10分現在3.16バーツ）

KASET – THAI HA PUBLIC COMPANY LIMITED
証券取引所はKASET株を本日11月9日より27日まで、現金取引のみのキャッシュバランスに。

KCE – KCE ELECTRONICS PUBLIC COMPANY LIMITED
2009年度第3四半期決算の純利益は1億2千3百万バーツ。前年同期は1千万バーツほどであった。

MINT – MINOR INTERNATIONAL PUBLIC COMPANY LIMITED
2009年度第3四半期決算の純利益はおよそ1億5千2百万バーツ。前年同期は3億7千6百万バーツであった。

ADVANC – ADVANCED INFO SERVICE PUBLIC COMPANY LIMITED
2009年度第3四半期決算の純利益はおよそ41億8千万バーツ。前年同期は45億3千万バーツであった。また、来年度1Q にも実施されるとされる3G通信免許入札にをなえて現金勘定を増やしている。

SAMART – SAMART CORPORATION PUBLIC COMPANY LIMITED
（タイ、カンボジア間の関係悪化に関して）カンボジアでのSAMART社のビジネスは通常通り。おそらく問題は激化せずに早目に鎮静化に向かうとの予想。

CGS – COUNTRY GROUP SECURITIES PUBLIC COMPANY LIMITED
来年度は顧客企業の上場を3～6社計画している。上場申請（ファイリング）は、来年年明けから順次行う予定

THAI – THAI AIRWAYS INTERNATIONAL PUBLIC COMPANY LIMITED
第3四半期の目標未達は受け入れるしかない。航空料金を値下げしたので第4四半期は売り上げが改善する見込み。

MFC – MFC ASSET MANAGEMENT PUBLIC COMPANY LIMITED
2009年度は利益の伸びを15-20％と予想。NAV（純資産）は当初計画に近い2600億バーツ。

DTAC – TOTAL ACCESS COMMUNICATION PUBLIC COMPANY LIMITED
Mobile Broadband Operatorとしての地位を目指す。3Gライセンス取得後に大きく動く予定。

FOCUS – FOCUS DEVELOPMENT AND CONSTRUCTION PUBLIC COMPANY LIMITED
経営陣は来年度半ばにも、新規8階建てコンドミニアム（建売マンション）建設価格3億バーツほどの物件を計画中。

THCOM – THAICOM PUBLIC COMPANY LIMITED
タイ-カンボジア関係が緊張しているが、現状ビジネスには影響がない模様。

にほんブログ村

So, today I found out a very interesting thing…I wondered for a long time if I could connect my printer (MFC-7420) to a non-x86 Linux machine (SPARC!) to have a print server. Well I failed…I failed again, but here’s how I eventually succeded:
Let’s take a look at what the filterMFC7420 CUPS wrapper (from the official Brother-Linux-Package for the MFC7420) does when it gets a file to print:
When you pass a ps file through the /usr/local/Brother/lpd/psconvert2 and then through rawtobr2 out comes a data file of an unknown type. But if you look at it with a hex editor, you see the following:
%-12345X@PJL
@PJL JOB NAME="Brother HL-XXX"
@PJL SET RAS1200MODE = OFF
@PJL SET RESOLUTION = 600
@PJL SET ECONOMODE = OFF
@PJL SET SOURCETRAY = TRAY1
@PJL SET MEDIATYPE = REGULAR
@PJL SET ORIENTATION = PORTRAIT
@PJL SET PAPER = LETTER
@PJL SET PAGEPROTECT = AUTO
@PJL ENTER LANGUAGE = PCL
E&u600D*t600R*b1030m5021w
This is crazy! The rawtobr2 binary just somehow translates the postscript file to some GDI/PJL-language-file! And it seems that they used the same language as for the HL-XXXX series of printers….this means, we could have full linux support without the proprietary Brother drivers. Which then means….my printer could run on my SPARC machines
Later, I proved this is really true:
Take one MFC-7420. Connect it through USB to a computer running Linux. Start the CUPS service. With a browser, go to http://localhost:631 – Administration tab. And click on Find new printers. Follow the instructions and then as printer driver select “Brother HL-5050 Foomatic/hl1250″ (the foomatic package needs to be installed!!) then finish. Set the printer options and print a test page
Hurray! We have it!

Unsere neue Einbauhilfe ist fertig.

Die Einzugsrolle hat die Brother Art-Nr.: LM4300001

Uns sind folgende Geräte bekannt:
Brother MFC-7420
Brother MFC-7820N
Brother MFC-7225N
Brother DCP-7010
Brother DCP-7025
Brother FAX 2820
Brother FAX 2920

weitere sind möglich.

Zum Artikel

Für Kunden, die diesen Artikel bei uns gekauft haben, ist die Anleitung kostenlos, die Schutzgebühr beträgt 6,90 Eur

Um den Brother MFC-9880 auf seine Ausgangskonfiguration zurückzustellen führen Sie folgende Prozedur durch.

HINWEIS !
Bitte beachten Sie, das sämtliche Einstellungen gelöscht werden und durch evtl. Fehleingaben, das Gerät, nicht mehr funktionsfähig ist! Falsche Eingaben in diesem Modus können zur Folge haben, dass grundsätzliche Funktionen des Gerätes nicht mehr verfügbar sind. Halten Sie sich deshalb bitte genau an die Anweisungen.

- Netzstecker ziehen

- drücken Sie und halten Sie die “Menü“ Taste weiterhin gedrückt während Sie den
Netzstecker GLEICHZEITIG wieder einstecken und die “Menü“ Taste
ca. 20 Sekunden gedrückt halten

- Im Display erscheint MAINTENANCE

- lassen Sie die “Menü“ Taste los

- drücken Sie jetzt auf dem Ziffernblock die “0“ und “1“

- Im Display erscheint PARAMETER INIT  (Das Gerät initialisiert sich neu)

- Im Display erscheint MAINTENANCE

- Im Ziffernblock die Tasten  “0“ und “1“ drücken

- Im Display erscheint PARAMETER INIT  (Das Gerät initialisiert sich neu)

- Im Display erscheint MAINTENANCE

- Die Tasten “9″ und “9″ drücken, um den MAINTENANCE Mode zu verlassen

- GGfls nochmal Netzstecker, am Gerät, ziehen

Bei bestimmten Modellen bestätigen Sie die Abfrage “Select?“ mit der “Start s/w“ Taste.

Je nach Modell haben die Tasten eine andere Beschriftung, z.B. “Menü“ = “Menü/Eingabe“ = “Funktion“ = “Sicherer Druck“ (nur MFC-9420) oder “Eingabe“ = “Menü/Eingabe“ = “OK“ Taste.

Bei bestimmten Modellen bestätigen Sie die Abfrage “Select?“ mit der “Start s/w“ Taste.

Ein Tip vom Drucker-Service-Kiel

We know that memory is always at a premium. So as a programmer we have to to ensure minimum memory consumption as possible and necessary to avoid memory leaks from the program. How can we detect memory leaks in our program.

MFC provides a structure CMemoryState to detect memory leaks in our program. This diagnostics method only help to detect memory leaks caused when memory allocated using the new operator is not deallocated using delete.

void DetectMemoryLeak()
{
   CMemoryState oldMemState, newMemState, diffMemState;
   oldMemState.Checkpoint();
   /* new memory is allocated in the heap */
   int *p = new int;
   /* heap memory is not yet deallocated */
   newMemState.Checkpoint();
   if(diffMemState.Difference(oldMemState,newMemState))
   {
      AfxMessageBox(_T("Detects Memory Leak"));
   }
}

CMemoryState will not address the leaks caused by malloc , LocalAlloc & GlobalAlloc.

Enviado por Alejandro González

El sábado 17 de octubre pasado fue otro día de MMA (Artes Marciales Mixtas, del inglés Mixed Martials Arts) en nuestro país. En la cúpula del Parque O’Higgins se dio lugar a la tercera edición de Master Fighters Championship.

Esta edición, titulada “Honor” por los organizadores, se destacó el GP -mini torneo- por los campeonatos de MMA y Kickboxing de 85 Kg.

El GP De MMA fue entre Sebastián Galaz (Bahamondes Dojo), Rodrigo Cabral (Team Cabral), Cristian Herrera (Gracie JiuJitsu Chile) y Juan Carlos “Nitro”Perez (Nitro MMA)

El evento destacó por las sorpresas. Galaz, quien proviene del kickboxing (47 peleas ganadas y 3 perdidas), debutó en el primer combate frente a Juan Carlos “Nitro” Perez. En un encuentro reñido, Perez se fue en busca del takedown, pero El Striking de Galaz dio la sorpresa. Pero, Galaz no dio tregua a Perez, el cual con el duro castigo , no pudo seguir al 2do round, debido al daño que este tenia en su rostro.

La segunda lucha clasificatoria del GP fue entre Cristian Herrera, del Gracie JiuJitsu Santiago y Rodrigo Cabral. La lucha fue rapida, se fueron en busca del takedown, Herrera lo logra dominar rápidamente y comienza a golpear el rostro de Cabral en reiteradas ocasiones. Éste último no le quedó otra alternativa que rendirse y darle la victoria a Herrerae.

Cabe Destacar la lucha de Francisco Landaeta y Juan Sebastián Yañez, en la cual, Landaeta demostró un excelente JiuJitsu, entró con actitud y seguridad, lo que le dio la confianza para aplicar un armbar inverso y llevarse la victoria.

GP de Kickboxing, fue una excelente super 4, Benjamín Arroyo fue la estrella de la categoría, derrotó sin problemas a Claudio Claros por Ko.

Lara derrotó a Irribara por Decisión De La Esquina de Irribara. El final fue clave, Arroyo sobresalió y obtuvo la victoria por Decisión De La Esquina de Lara, donde decidieron no seguir.

Se lamentó la lesion de Patricio Veas, quien se fracturó la Tibia y el Peroné en su combate frente a Rodolfo Guzmán. La pelea fue pareja, pero al intercambiar golpes en el 2do round, la pierna de Veas cedió.

La Final del GP MMA Cristian Herrera vs Sebastián Galaz.

En la lucha decisiva, se fueron a buscar el takedown. La poca experiencia de Galaz luchando en el Suelo, le pasó la cuenta al recibir el armbar de Herrera. Esta llave causó que Galaz palmeara y diera la victoria a Herrera para coronarse campeón.

Resultados Finales:

1er Clasificatorio GP Kickboxing:

Eladio Lara derrota a Francisco Irribarra Por Abandono.

1er Clasificatorio GP MMA

Ivan Galaz derrota a Juan Carlos “Nitro” Perez por TKO (Decisión Del Medico)

Esteban Salinas vs Jose Rivas Termina En Empate

2do Clasificatorio GP Kickboxing

Benjamín Arroyo derrota a Claudio Claros por KO

2do Clasificatorio GP MMA:

Cristian Herrera Derrota a Rodrigo Cabral por TKO (Puños)

Tomas Vasquez derrota a Eric Galdames por Decisión Dividida

Francisco Landaeta derrota a Juan Sebastián Yañez por Submission (Armbar)

Rodolfo Guzman derrota a Patricio Veas por TKO (Lesion)

Final Kickboxing GP:

Benjamín Arroyo derrota a Eladio Lara por Abandono

Cristian Parra derrota a Marco Contreras por Abandono.

Final MMA GP:

Cristian Herrera derrota a Sebastián Galaz por Submission (Armbar)

____________________________________
ATSteveDuncan  ®  The Prodigy Iceman…

The benefits of using the Model-View-Control (MVC) pattern in our development projects

is that we can completely decouple our business and presentation application layers. Furthermore, we will have a completely independent object to control the presentation layer.

via Introduction to Model View Control (MVC) Pattern using C#.

MFC had a pretty stacked fight card on the second of October, a lot of fighters headlining the event! They had Travis Lutter, Jason McDonald, John Alessio, Antonio McKee, Pete Spratt and a lot of other big names. So needless to say there was a lot of talk about how some of the fights were going to pan out that night. I know I was interested in seeing some of these fights and couldn’t wait to read/hear about them after (seeing how I couldn’t be there to watch them live)! All my picks ended up winning (which never happens) so I was really excited about that.

But like anything there is always an aftermath of something after a huge event like MFC 22, whether it be where so and so goes from there, or someone not making weight (and the reasons why), or someone losing really bad I mean the topics are endless.

I think for this event the Pete Spratt and Nathan Gunn got a lot of attention on the MMA forums and just chitter chatter over the water cooler the next day at work.

Personally when I read that Pete Spratt was fighting in the MFC again I was shocked, shocked because I had watched and heard about his last fight there against Ryan Ford. I don’t know if anyone else has seen the fight, and I’m not trying to take anything away from Ryan (because he’s a good fighter as well) BUT there were a lot of “odd” factors in that fight, and I think that there is a lot of stuff that happened that maybe shouldn’t have.  Like how nobody heard the bell in that place and Herb Dean goes in to stop the fight and then lets it go? Which made no sense, I’ve been to an MFC fight WHEN Ryan Ford was fighting in a big fight and I clearly heard the bell and I was AWAY from the ring. A lot of people believed that maybe Pete Spratt got “screwed” in that fight? I’m not sure how the rest of the fight would have paned out however I do know there were a few BAD calls that maybe could have been prevented that obviously played a factor in that fight.

So to see Pete Spratts name on the fight card, my jaw dropped I was sure it was a typo until I got official confirmation. Regardless I was glad to see him fighting in Canada, and from what I researched his opponent wasn’t too shabby either. I obviously picked Spratt to win that fight but knew that Gunn had a lot to bring to the table.

Unfortunately for me I couldn’t make it out to the MFC (doesn’t mean I didn’t want to go), SO i was just hoping that I could catch the fight on HDNET or maybe online somewhere (which it was)!

(WATCH FIGHT HERE)

So… this is how I feel about the much talked about fight:

In round one Gunn managed to get Pete down a hell of a lot, but once he was down there he really didn’t do anything I think he maybe punched him all of a handful of times from the bottom, like the commentators said it wasn’t a devastating win of the round. But with that Spratt was making attempts on the bottom for submission too, like Gunn was in control but Spratt wasn’t just being lazy and not doing much I think I seen him do more to get out of things on the bottom then I have in his other fights, which means that NO he’s not an expert on the ground just yet BUT he obviously KNOWS its a weakness of his and I think he is working on it? Then again I’m not a die hard Spratt fan so I guess  thats just my opinion. I think that if Gunn secured his positions (which he did most times) and threw in some ground and pound that the fight could have been a bit different. Again, I’ve never been in a fight in a ring so maybe Gunn had a different mind set… regardless he won the first round clearly with all those take downs and dominate positions like taking Spratt’s back and what not.

Round two is where the controversy starts, Spratt comes out pretty hard and hits Gunn with some hard looking shots. Gunn was trying to compose himself and Spratt just kept moving forward with the blows, but Gunn managed to take him down, but once he got him on the ground and was able to start some ground and pound he didn’t, maybe he felt like he didn’t secure his position enough to do so (who knows)…

THEN it happens, Gunn puts Spratt in the ropes and at first glance it looks like Spratt dodges through the ropes to maybe catch a break and avoid being taken down again, but unlike most people I rewinded the video to watch it again. And it really looked like Pete looked like (to me) he was defending the take down and went to do something and was pushed a little bit and when he went to catch himself he felt through the ropes. After that when Pete was making his way back in Gunn is sitting there taking whatever air he can in, his arms are over his head and Pete heads to the middle of the ring and thats where they start the fight again. I think there might be one more take down before Spratt throws an uppercut that misses him by a few seconds (which could have knocked him out or hurt him) and then connects with that big one that ends the fight.

NOW, KUDOS to Gunn for stepping up to the plate to a guy who has the experience over him, what an excellent way of testing yourself in there. I know a guy who did the same thing and tested himself in there. That takes a lot to do, especially if you have a perfect record.

But after that fight I started to notice some talk that was happening (as I expected there would at some point).

Now… I don’t know if anyone is on Pete Spratt’s facebook page but before (like way before) I knew he was fighting or even read it I remember seeing something about him going for surgery on his knee, I’ve never had that done but I would assume depending on the surgery it just doesn’t heal and work fine in a night. And personally watching that fight I never would have known that there was a problem there. Second, people are so quick to judge and it amazes me.

I could sit here and say Gunn did nothing but take Spratt down and lay on him, and Spratt yes got out of things and attempted some stuff but wasn’t really aggressive enough, BUT I’m not and I won’t because both men did well, and obviously both need to work on things which fighters do after every fight. WIN or lose they go back (well the good ones) and figure out what they can improve for the next one.

And for people so say things like:

“Nice trick by Spratt diving through the ropes to get the fight stood up.”

“The rest of the fight was full of sloppy BJJ and bad sprawls”

“The fight was mostly Pete’s awful wrestling and exposing his back, it was long boring grind, until that. POW!”

AND believe me the list goes on and on just  for Spratt but for both guys. The way I look at it is Its easy to stand by the side lines and say things, Pete never said he’s was an amazing BJJ practitioner SO for someone to say stuff about it as if he’s suppose to be amazing boggles my mind. I’m confident he knows its a “hole” in his game and I’m confident he’s working on it but some people don’t pick it up in a year or so, especially if they never really focused on that part of things. I came from a wrestling background and maybe its just me but I found it frustrating going from that to BJJ. SOME people learn faster then others.

A lot of people said that Gunn looked really gassed and should have had more to offer Spratt but I mean who are they to judge? Most of the people talking are huge fans and not that there is anything wrong with that but really if you’ve never been in there maybe have some constructive ways of critiquing a fight instead of picking it apart with negative comments.

That’s another thing I give these athletes kudos for! Putting them selves out there  and fighting in front of decent size crowds, and trying to put on a good fight for the next day to come online or open a paper and see how “poorly rated” it was. I’m sure that’s is such a nut kicker its not even funny.

I mean its public knowledge to anyone who’s followed my blogs I am NOT a fan of Brock Lesnar…. Do I give him credit where it is due YES! BUT you would never catch me just crap talking I try to have constructive criticism there as well.

I think these people forget they that these athletes have families they have to take care of. I remember reading one post that money must mean more to sprat then a falling out or something like that with the MFC. WHY wouldn’t Pete want to fight in the MFC they seem to be one of the up and going organizations in Canada, their shows almost always sell out, they are on HDNET fights which gives him decent exposure, and I’m sure the paycheck isn’t too shabby either? SO why not? He’s got a family just like most of the people writing on these forums. If the MFC had a problem with Spratt why ask him to come back in fight? Because they also have a family to take care of and they know that he would bring in some more fans to watch. Business is Business.

I’m not sitting here and bashing anyone, and that wasn’t my objective by writing this. I just wish people would open their eyes sometimes and be a bit more professional.

I respect Nathan Gunn, for a lot of reasons and respect him even more because DESPITE what happened in that ring he had this to say

“was an honour to go to battle with you Pete and a privilege to meet you afterwards. You are a class act and great fighter and man. I look forward to seeing you perform many more times and wish you much luck on your continued journey back to the top. Take care and congrats”

Christina

MFC – MFC ASSET MANAGEMENT PUBLIC COMPANY LIMITED
不動産投資ファンド２つをエキジット準備。時価30億バーツ程度。

THCOM – THAICOM PUBLIC COMPANY LIMITED
タイコム2号の代替機用途の中古衛星はICT情報通信向けに提供できるものは３機しかなく、そこから選択するしかない。と関係筋は伝えた。

SCAN – SCANDINAVIAN LEASING PUBLIC COMPANY LIMITED
SCAN取締役会はピンムック・セーナーディサイ氏を取締役に選任すると共に、１０月２８日に株主総会を開催することを決定。

KCAR – KRUNGTHAI CAR RENT AND LEASE PUBLIC COMPANY LIMITED
車リースのKCARは、本年はリース車の返却が増え頭が痛い。が、（車を担保にした）信用貸しが伸びて、リースの不振を補っている。本年度は5-10%の成長を目指している。

AS – ASIASOFT CORPORATION PUBLIC COMPANY LIMITED
本年度総売上高は10%の伸びと予測。新オンラインゲーム「後ランティカ・オンライン」が、急速に市場に受け入れられたため。

UT – UNION TEXTILE INDUSTRIES PUBLIC COMPANY LIMITED
63.3ライ（1ライはおよそ1600平米）を、シャープ・アプライアンス社に売却。価格は約5億3千7百万バーツ。

NMG – NATION MULTIMEDIA GROUP PUBLIC COMPANY LIMITED
株主のために、ネーション・ブロードキャスティング社の株をIPO価格で販売予約へ。比率は９：１ （Info Quest 9月24日配信）

ピチットMCF投資マネージメント会社CEOは取材に答えて、「タイの株式市場はまだ成長する余地があると見ている。大きな理由の一つが外国人投資家が投資リスクを取り始めていること。また、株式市場への投資金の流入について、現在外国人投資家の投資資金の流入金額は400億バーツに達するが、これは（昨年の内政・世界経済などの）危機的状況の影響下で外国人投資家のタイ国内から引き上げた金額2000億バーツのうちの20%にしかなっておらず、決してまだ大きな金額であるとは言えない。また同時に西側諸国の資金の流れは、ようやくタイを含むアジアに向かい始めたばかりである。
ここで、2010年度のSET Indexの状況を予測すれば、750ポイントから780ポイントの間。最悪ケースで680ポイント、最良のケースで820ポイントと予測している。」と語った。（ストックウェーブ 9月23日配信）

Well, MFC has lots of weird aspects. Basically MFC is a framework. What is a framework? Framework is a wrapper of API to make the API easier to use.
However, when MFC is compared to ToolBox which was most popular during similar period of time, MFC is not as easy to use as ToolBox. ToolBox is, however, API not framework.

Here I would like to show one example why MFC is bad and why its design is bad. Let’s think about CListCtrl. It is a list control or table control if you think of it in the context of Mac OS X. What do you want to do with it?
Let’s summarize some of them.

• Populate ClistCtrl
• Retrieve row item or column data
• Change properties like text color, background color, font and so on for row items.
• Customizing the UI
• and so on

First, to manipulate the data or to populate the CListCtrl, this class itself doesn’t provide consistency. Why am I talking about consistency? Let’s take a look at CStatic or CEdit. On Windows, you can set a control variable for them or data variable for them. A control variable is like :

CEdit *editBox

, while data variable is like :

CString editBoxString

To manipulate the value itself, data variable is easier. However to control the widget itself, you should use the control value.
With Cocoa, you don’t need to have this separate mechanism. In Windows point of view, it is like to declare CEdit variable and the CEdit class provides all the methods to manipulate the data value. Or with Cocoa binding, things can be done much more easily.

It does not mean that it is impossible to manipulate data with the control variable. With some widget, or control, it is not easy or is not possible at all.

Here, with CListCtrl, there is no “data” variable unlike that of CEdit or CStatic. So, you should manipulate the data with the CListCtrl itself. So, there is no consistency.

Second, it is very difficult to retrieve row item or data.
GetItem() is for that, but if you look up MSDN document for it, it is not clear how to retrieve an item you want.
Here is explanation on what it does.

Retrieves some or all of a list view item’s attributes.

The LVITEM structure specifies or receives the attributes of a list view item.

However, it doesn’t say about how to do so.

There is something which is even worse.
Let’s take a look at the LVITEM parameter.
What is lParam? What does it supposed to contain? There is no explanation about it in MSDN document.

Let’s assume that you want to customize the CListCtrl. You want to set a bold font for a specific row item or column. Does CListCtrl provide such method? No. Also, there is no each way to retrieve ith item on a CListCtrl. Among them, one easy thing is to set a text color or a background color of a item. Well.. how to to so? There is no explanation about it.
Well.. you can implement a message handler for WM_CUSTOMDRAW message. However the MFC document for CListCtrl doesn’t even contain link for the message. You should look up Win32 document. Isn’t it strange? Framework is a wrapper for API to make API easy to use. However, For MFC, if you want to do some common thing like this, the API, or Win32, should be revealed.

Third. Let’s think about a situation in which you want to set a bold font for some items. There seems to be no way to do so.
Creating a CListCtrl Class with Item Style Features (CListCtrlStyled Class) from CodeGuru introduces a customized CListCtrl clas to do that.

Let’s take a look at some source codes from the class.

void CListCtrlStyled::SetItemStyle(int nItem,int nSubItem,DWORD Style,bool redraw)
{
	// We must retrieve the Style info structure of this item
	//
	LVITEM pItem;
	InitLVITEM(nItem,0,&pItem);

	LS_item * lpLS_item = NULL;
	lpLS_item = (LS_item*) pItem.lParam;

	if(nSubItem > 0)
		lpLS_item = lpLS_item->subitems[ nSubItem - 1];

	// no we can update the style
	//
	lpLS_item->StyleFlag = Style;

	DWORD mask = LIS_BOLD | LIS_ITALIC | LIS_UNDERLINE| LIS_STROKE ;
	lpLS_item->in_use = (Style & mask) > 0;

	// if any font exist for this item then delete it
	//
	this->Free_LS_font(lpLS_item);

	// Redraw it
	if(redraw)	CListCtrl::Update(nItem);
}

void CListCtrlStyled::InitLVITEM(int nItem,int nSubItem,LVITEM * pItem)
{ /*
  typedef struct _LV_ITEM {
    UINT   mask;         // see below
    int    iItem;        // see below
    int    iSubItem;     // see below
    UINT   state;        // see below
    UINT   stateMask;    // see below
    LPSTR  pszText;      // see below
    int    cchTextMax;   // see below
    int    iImage;       // see below
    LPARAM lParam;       // 32-bit value to associate with item
   } LV_ITEM;
  */
	pItem->mask = LVIF_PARAM;
	pItem->iItem = nItem;
	pItem->iSubItem = nSubItem;
	pItem->state = NULL;
	pItem->stateMask = NULL;
	pItem->pszText = NULL;
	pItem->cchTextMax = NULL;
	pItem->iImage = NULL;
	pItem->lParam = NULL;
	CListCtrl::GetItem(pItem);
}

In InitLVITEM() method, it calls GetItem(). What it does is to retrieve lParam value in LVITEM. Then in SetItemStyle(), it calls :

	LS_item * lpLS_item = NULL;
	lpLS_item = (LS_item*) pItem.lParam;

	if(nSubItem > 0)
		lpLS_item = lpLS_item->subitems[ nSubItem - 1];

Hmm.. lpLS_item is once set to lParam. And it is set to lParam’s subitems[].
Then based on the value, it tries modify the variable to set a font face.
To do this, you should know that what the lParam means and the data structure lParam contains. Also, you need to know howdata structure its subitems[] looks like.

But where is explanation on them is? I can’t find anything on MSDN.

There are a lot of things in MFC like this.
Classes are not prepared to handle things easily, and its MFC documentation doesn’t have any link or explanation.

I don’t understand why MS doesn’t provide good documentation about its classes. The bad design of MFC can be understood if we consider when it was designed. However, if MFC designer at MS still want to keep the MFC for native environment, they should do something about it.

Let’s have a look to see what the tool CppDepend shows when comparing MFC 2005 with MFC 2008 ones. I will use a few CQL Queries to get fact from the code base of the Framework.

A view of the work achieved

SELECT METHODS WHERE CodeWasChanged OR WasAdded

The following treemap shows in blue, new methods (i.e WasAdded) and methods that have been refactored (i.e where CodeWasChanged). A rectangle represents a method and the size of the rectangle is proportional to the size of the method (in terms of Code Line ). It is pretty impressive to see that a big part of the framework is still evolving.

The Info panel of CppDepend shows that MFC 2008 is bigger twice than MFC 2005

New Types

SELECT TYPES WHERE WasAdded

367 new types added including:

• Menus
• Toolbars
• Panes
• Ribbon Control
• Outlook Alert
• Controls
• Dialog Boxes
• Customization
• Visualization

New Namespaces

SELECT NAMESPACES WHERE WasAdded

Only 1 namespace was added it contains classes to integrate Winform into MFC.

Methods where visibility changed

Only the visibility of the CHtmlEditCtrl destructor was changed from protected to public.
It was a design bug in MFC 2005, you can discover here why it was problematic.

Types Removed

All classes relative to ISAPI were removed; it’s a break change that can be very embarrassing for developers who used them before.

Conclusion

The major evolution of MFC includes a new types to support modern user interface (UI) elements such as the Office Fluent UI, docking windows and MDI tabbed windows similar to those used in some releases of Visual Studio, enhanced toolbars, a rich new set of controls, support for controlling the overall visual style, support for desktop alerts, and much more.

but no big changes concerns the MFC design,it’s true that MFC now use more manager classes as controlers than before

but the design of the new functionalities still unchanged, for example only one namespace is added.

The Microsoft Foundation Class Library is an application framework for programming in Microsoft Windows. Written in C++, MFC provides much of the code necessary for managing windows, menus, and dialog boxes; performing basic input/output; storing collections of data objects; and so on.

The MFC framework is a powerful approach but using it impacts the design of the application, it’s very intrusive and we have to be careful of how we use it.

Let’s analyze MFC8 with CppDepend to discover its code quality and design.

CppDepend is a tool that simplifies managing a complex C++ code base. Architects and developers can analyze code structure, specify design rules, and plan massive refactoring, do effective code reviews and master evolution by comparing different versions of the code.

CppDepend supports the Code Query Language (CQL) for maximum flexibility. Basically CppDepend considers your code as a database and you can write some CQL statements to query and check some assertions on this database. As a consequence, CQL is similar to SQL and supports the SELECT TOP FROM WHERE ORDER BY pattern.

With CppDepend we analyze the quality of implementation and also the design of MFC.

A quality of implementation is important for developer who debug inside MFC,indeed not all things work as we like and sometimes we have to look inside the library code so if it’s not well implemented it complicate the task when debugging.

A design of MFC is very important for developers because it impact the design of the application because it’s very intrusive.

MFC General Information’s:

The dependency Graph shows that MFC uses 149 methods from ATL and 1014 from Windows API, and there’s general Information’s about MFC:

Code Implementation:

Naming Rules:

Let’s execute the following CQL request:

WARN IF Count > 0 IN SELECT FIELDS WHERE !NameLike “^m_” AND !IsGlobal

The blue squares represent the result of the query, so almost 50% fields don’t begin with m_”.

And what about methods naming:

WARN IF Count > 0 IN SELECT METHODS WHERE !NameLike “^[A-Z]” AND !(IsClassConstructor OR IsConstructor) AND !IsInTierProject AND !IsGlobal AND !NameLike “^~” AND !NameLike “^operator”

There are just some few methods that not begin with Upper case.

Cyclomatic Complexity:

Cyclomatic complexity is a popular procedural software metric equal to the number of decisions that can be taken in a procedure.
We can also consider that a method is complex if NbLinesOfCode,NbParameters or NbBariables are great than a defined values.

SELECT METHODS WHERE (NbLinesOfCode > 100 OR CyclomaticComplexity > 20 OR NbParameters > 5 OR NbVariables > 8 )

So 706 methods are candidates to refactoring, but the request can be changed, it’s depending on the choice of the complexity criteria for each team.

Comments:

SELECT METHODS WHERE NbLinesOfComment > 0

Almost all classes are commented so developers can have an idea of what a method does particularly when debugging inside MFC.

Let’s see if all complex methods are commented.

SELECT METHODS WHERE (NbLinesOfCode > 100 OR CyclomaticComplexity > 20 OR NbParameters > 5 OR NbVariables > 8 ) AND NbLinesOfComment ==0

There are just few complex methods not commented.

Design:

No existence of namespaces:

The namespace is an important concept to design application, it isolates functionalities under a module and provides a logical grouping, it can also make a library simple to use.
Unfortunately MFC don’t contain any namespace in spite of the existence of different functionality (GUI, OLE, Database, Containers …).

Global functions and variables:

MFC contains 786 global functions and 338 global variables, its lot for an object oriented framework.

Inheritance:

SELECT TYPES WHERE NbBaseClass >0

Almost all class has at least one base class, it cause a high coupling between classes.

Types Cohesion:

The single responsibility principle states that a class should have more than one reason to change. Such a class is said to be cohesive. A high LCOM value generally pinpoints a poorly cohesive class. There are several LCOM metrics. The LCOM takes its values in the range [0-1]. The LCOMHS (HS stands for Henderson-Sellers) takes its values in the range [0-2]. Note that the LCOMHS metric is often considered as more efficient to detect non-cohesive types.
LCOMHS value higher than 1 should be considered alarming.

WARN IF Count > 0 IN SELECT TYPES WHERE LCOMHS > 0.95 AND NbFields > 10 AND NbMethods >10 AND !IsGlobal ORDER BY LCOMHS DESC

31 types from 529 are considered non cohesive.

Dependency between Classes:

The option Direct & Indirect Weight of use the Dependency Structure Matrix is the perfect tool to let users know where the code structure is tangled with dependencies cycles.

The screenshot below showsthat the 2 classes CDocument and CCmdUI are involved in a cycle of minimum length 5.

The whole dependency matrix shows that almost all MFC types are coupled directly or indirectly.

Coupling:

The efferent coupling for a particular type is the number of types it directly depends on. Types with high efferent coupling are more complex than others,CppDepend propose a search panel, it’s like a wizard that help you construct query easily.

Let’s search for Types where efferent coupling is more than 30.

Doc/View Concept:

MFC separates data management into these two classes. The document stores the data and manages printing the data and coordinates updating multiple views of the data. The view displays the data and manages user interaction with it, including selection and editing.

In dependency graph CDocument and CView are mutually dependant and usually the model don’t have to know the View and it must be independent of any external framework.

The model has to be as simple as possible with simple types and without any unnecessary coupling.

The following CQL request demonstrate that CDocument is highly coupled with GUI classes:

SELECT TYPES WHERE IsDirectlyUsedBy “CDocument“

The goal is to reuse the same model in different projects (Console, Gui, WebService, …) and if our model is the CDocument we can’t reuse easily in other projects.

Recommendation:

Never use CDocument as model but use it just as controller to refresh views.

MFC Automation Server :

CDocument can be used also as COM Component, but CDocument is coupled with CView and using CDocument as COM component can occur some unexpected limitations and problems.

When we instantiate a CDocument as COM Component a handle of view is created due to the coupling Doc/View so the number of instances to create is limited by the number of window handles that can be created, and the problem occur particularly if the instances are created in a no desktop session, in this case the number of handle that can be created is very limited by default.

Recommendation:

Avoid using CDocument as COM component, keep it simple and use ATL instead it’s more simple and flexible.

Use or don’t use MFC?

MFC is well implemented but not really object oriented and the classes are high coupled, so be careful when using it and avoid any unnecessary coupling, for example prefer using ATL for COM component and STL for containers.

It’s preferable to avoid as possible the coupling of your model with Doc/View concept, it make your design less flexible and add more complexity.

The goal is to spend more time in developing the business layer and isolate any technical layer will be very advantageous:

· Human resources department don’t need to spend a lot of time to search for MFC gurus; maybe just few MFC developers will be sufficient.

· Developers don’t add a complexity of a framework to the complexity of what’s they implement.

· Reusing easily the business layer in other context (Web Services, Console,…).

So keep it simple and isolate the impact of any technical framework used, for that be careful for any unnecessary coupling.

La nouvelle secoue mais ne surprend pas. Après la fin des options d’Helios chez Desjardins, les réductions de protection chez Sunlife et la fermeture pure et simple de tout le département de placement d’AXA, au tour de Manuvie de sabrer dans ses produits d’investissement. Le 2 octobre 2009, la Financière Manuvie mettra la hache dans TOUS ses fonds distincts. Fini les garanties généreuses. L’assureur a évalué ses risques liés aux 20 milliards sous gestion de toutes ses familles de fonds de placement garantis et ne peut plus continuer à en offrir autant. Les clients détenteurs de contrats émis avant le 2 octobre 2009 seront rassurés d’entendre qu’ils bénéficieront de toutes les anciennes protections. Cependant, les options de placements seront modifiés pour restreindre certains fonds jugés maintenant trop volatils, donc coûteux à couvrir.

Ainsi, les FPG, FPG Perspective, CPLM, PPLM, CAP Maritime, FPG Sélect et RevenuPLUS ne seront plus offerts à de nouvelles souscriptions. En remplacement, dès le 5 octobre, les investisseurs pourront utiliser les FPG Sélect de nouvelle génération avec 3 options. Une appelée PlacementPlus, qui vise l’accumulation du capital. Une deuxième; RevenuPlus 2 qui propose un décaissement de 5% à vie à partir de 65 ans seulement et enfin, SuccessionPlus qui protège le capital pour les héritiers.

Le message à retenir: aucune de ces options ne protégera complètement le capital investi du vivant. La protection minimale légale, impose cependant une garantie de 75% du principal à l’échéance du contrat, soit au 100 ème anniversaire du titulaire. Autant ne plus parler de protection. Ainsi, les garanties à 75 ou 100% au terme de 10 ans, comme c’était la tradition, feront maintenant partie des souvenirs.

Pourquoi laissez tomber une telle protection du capital? Parce que le risque existe et la crise de 2008-2009 a laissé ses marques. La base de données Paltrak de Morningstar démontre d’ailleurs toute l’utilité d’une protection sur une décennie. Plus de 500 fonds et indices de marché sur un univers qui en compte 2200, affichent un rendement annualisé négatif pour la période couvrant août 1999 à août 2009. De ceux-ci, on compte même de grandes vedettes d’autrefois comme les LondonLife, RBC et AGF Action Américaines. Aucune compagnie de fonds n’échappe au carnage. Suggestion pour la TD, le Fonds TD Valeurs Sûres américaines, n’est plus tout à fait sûr. 1000$ investi il y a 10 ans ne vaut plus que 590$.  La calculette des actuaires de Waterloo a aisément fait comprendre que plus de 22% de risque, ça devient énorme.

Les grands gagnants de cette nouvelle seront les actionnaires de Manuvie, du moins à court terme.

The location and size of a dialog box,

as well as the location and size of controls within it,

are measured in dialog units (DLUs).

A DLU is based on the size of the dialog box font, normally 8-point MS Sans Serif.

A horizontal DLU is the average width of the dialog box divided by four.

A vertical DLU is the average height of the font divided by eight.