Question
[IDCS2 Mac] Bothersome "High ID" Assert
Hi Folks,
Have any of you encountered this...
I just got an InDesign Prefix ID and it is causing the following assert to fire when I quit the ID 4.0.5 debug build with my plug-in loaded.
StandardBossIterator::Next() - This tag has a rather high ID: 0x105d03. Is it valid?
The exact same assert happens at least 5 times when quitting ID Debug. It's annoying because I have to click through each assert in the CodeWarrior debugger. My main concern is that I'm afraid that I'm going to miss a serious assert thinking that it's just the "high ID" assert.
I'm using other Implementation IDs (e.g., for a kDialogBoss' observer and dialog controller) that don't cause this assert. The assert references the ID of kMyPictureControlViewImpl (see below):
My Adobe assigned ID is 0x105d00, so this number is within my assigned range, so the answer to the assert's question is, "YES!!! it is valid, and please stop asserting!." ;-)
I tried using an ID I have from an old project (a much lower ID number), and the assert does not fire. I'm using the latest CS2 SDK and ID 4.0.5 Debug.
Any ideas on why this is happening only for the one boss, and how to keep it from firing?
Thanks in advance!
-- Jim
Have any of you encountered this...
I just got an InDesign Prefix ID and it is causing the following assert to fire when I quit the ID 4.0.5 debug build with my plug-in loaded.
StandardBossIterator::Next() - This tag has a rather high ID: 0x105d03. Is it valid?
The exact same assert happens at least 5 times when quitting ID Debug. It's annoying because I have to click through each assert in the CodeWarrior debugger. My main concern is that I'm afraid that I'm going to miss a serious assert thinking that it's just the "high ID" assert.
I'm using other Implementation IDs (e.g., for a kDialogBoss' observer and dialog controller) that don't cause this assert. The assert references the ID of kMyPictureControlViewImpl (see below):
Class
{
kMyPitcureWidgetBoss,
kPictureWidgetBoss,
{
IID_ICONTROLVIEW, kMyPictureControlViewImpl,
}
},
My Adobe assigned ID is 0x105d00, so this number is within my assigned range, so the answer to the assert's question is, "YES!!! it is valid, and please stop asserting!." ;-)
I tried using an ID I have from an old project (a much lower ID number), and the assert does not fire. I'm using the latest CS2 SDK and ID 4.0.5 Debug.
Any ideas on why this is happening only for the one boss, and how to keep it from firing?
Thanks in advance!
-- Jim
AdChoices