Debugging a plugin on a WIN PC

hello,
i am trying to debug my plugin. when i start the debugger i get many assert dialogs. i have to push the skip button many times till indesign is started.
how can i say indesign not to show this assert dialog and instead print the messages to a log?
thanks,
juergen

I agree with Patrick. If you run into asserts, it means you are doing something that InDesign does not like and you need to fix the underlying problem.
One of the most numerous asserts I received when I first started debugging had to do with PMStrings in dialogs. ID wants you to either use strings stated in your .FR file or use strings that are set to kNoTranslate. I developed this macro:
PMSTRING(X) PMstring(X, -1, PMString::kNoTranslate)
Using it to declare PMStrings removed all asserts that were caused by creating PMString dialog labels on the fly.
BTW, I also solved the problem by adding strings to the string table in the .FR file. Its a bit more time consuming, but the purists might say that doing it that way is the more correct way, and they are probably right.
If you are getting specific asserts that you do not know how to track down, please tell us what they are. We can then address your problem in particular.
R,
John

Similar Messages

How to debug the plugin?

now i can debug the plugin throught avalertnote message box or outputdebugstring ? but can not debug into the adobe ?

Hi,
If you have the plug-in open in your IDE (Visual Studio or Xcode ), and you have the target set correctly in the project settings. then if you set a break point in the code, and select debug from the build menu, then assuming your code is run your break point should be hit and execution should stop at that point.
If you want to provide more information about what OS and IDE you are using then we may be able to provide more assistance on your problem?
Malcolm

Mac PPC/CS2: Problems debugging a plugin

Hi
I try to debug a plugin, but it doesn't work.
- I have installed the debug version of Indesign CS2
- I have build the debug version of a SDK sample (Basic dialog)
- I have opened the SYM file in CW9 Symbolics Window
- I have opened the AdobeIndesign.app from the package Adobe Indesign in CW9 Symbolics Window
- I start Adobe Indesign in the Symbolics Window
- I set a breakpoint in SDKPluginEntryPoint (GetPlugin)
Indesign starts and after a while, it breaks. But I don't see the source code, I see only an assembler code.
- What could be wrong?
- Have I anything forgotten?
Thanks for every help.
Kind regards
Hans

You are not doing much wrong here - the problem is CodeWarrior: it's source debugger doesn't work correctly with this SDK.
Debugging mac plugins is about using the TRACEFLOW macro to output to the DebugWindow - an SDK tool that displays the TRACEFLOW output to a floating window.
Be aware that the TRACEFLOW macro is only sending output from the Debug build - so you don't have to take care for the Release build.
Alternatively you could also use a log file - there is a sample of this in the SnippetRunner project - if I recall it correctly . . .
I do understand your frustration about CW source debugger: I had the same a few years ago. Since then I do not use source debuggers in my programming anymore: it was like stopping tabacco or turning OFF the TV set definitively - the end of an addiction . . .
HTH
Best regards
Patrick Perroud

Getting incorrect values for linkQueryResult (ILinkManager) while debugging our plugin in Adobe InDesign CC debug

Hi,
We have added some functionalities in PanelTreeView sample source. In that, we are getting incorrect values for linkQueryResult (ILinkManager) while using InDesign CC debug. But in release version we are getting the correct values for linkQueryResult (ILinkManager). So when debugging our plugin InDesign CC debugger has stopped working. Please find the below source,
IDocument* document = Utils<ILayoutUIUtils>()->GetFrontDocument();
if(document == nil)
//CAlert::InformationAlert("Doc Interface Not Created");
break;
IDataBase *db = ::GetDataBase(document);
InterfacePtr<ILinkManager> linkmanager(document, UseDefaultIID());
if(linkmanager == nil)
//CAlert::InformationAlert("linkmanager Interface Not Created");
break;
LinkQuery Query;
ILinkManager::QueryResult linkQueryResult;
linkmanager -> QueryLinks(Query, linkQueryResult);
for (ILinkManager::QueryResult::const_iterator iter(linkQueryResult.begin()), end(linkQueryResult.end()); iter != end; ++iter)
InterfacePtr<ILink> iLink(db, *iter, UseDefaultIID());
if ( iLink )
InterfacePtr<ILinkResource> resource(linkmanager->QueryResourceByUID(iLink -> GetResource()));
ILinkResource::ResourceState rs = resource->GetState();
PMString fileName = resource -> GetLongName(kTrue); //gets full path
CharCounter lc=fileName.LastIndexOfCharacter('.');
PMString *exten = fileName.Substring(lc+1,3);
if((*exten).Compare(kFalse,"xml")==0)
xmlDataLinkName = fileName;
Kindly help us if anyone has idea regarding this issue.
Thanks,
VIMALA L

Hi Vimala L,
try to replace
ILinkManager::QueryResult linkQueryResult;
by
UIDList linkQueryResult(db);
Markus

PSE 13 Plugins on a Win 7 64 bit OS

Installed PSE 13 a Win 7 machine. Only one Plugin (of many) recognized. All plugins known & executable on PSE12.
Plugins exist in c/program files/Adobe/Photoshop Elements 13/Plug-Ins-12 but not in Plug-Ins.
Link to or file moves from Plug-Ins-12 to Plug-Ins not recognized.
Any Ideas.....else PSE13 is toast since I rely heavily on the plugin suite.

Elements 12 was a 32-bit program even if run on a 64-bit Windows operating system. For that reason, the 32-bit plugins would work.
If you installed the 64-bit version of Elements 13, the previous 32-bit plugins won't work.
You'll have to go back to the companies that made your 32-bit plugins and see if they have 64-bit ones you can download.

Debugging a plugin

I am having trouble with a plugin.
When I access it from the menu I get the message box "Could not complete the Export command because there is not enough memory (RAM)". The message box appears before my PluginMain is called.
It seems to be related to the linking somehow; when I do not link against a specific library my plugin works. Weirdly, it also works when I am linking against the library and not referencing any stl containers. The dll is loaded (DllMain() is called) but PluginMain() is never called.
dumpbin /exports gives me this output:
Section contains the following exports for photoshopexporter.8be
00000000 characteristics
463B2018 time date stamp Fri May 04 13:59:20 2007
0.00 version
1 ordinal base
1 number of functions
1 number of names
ordinal hint RVA name
1 0 00001163 PluginMain
Summary
52000 .data
2000 .idata
F7000 .rdata
2B000 .reloc
2000 .rsrc
449000 .text
When looking at the dumpbin output of the "Outbound" sample I notice that the PluginMain() has an RVA of 1000. There is also a comment in the "Outbound" source saying "...most development systems require [PluginMain] be the first routine in the source." Is there a way to control the RVA of an exported function, and does it matter to Photoshop?
I have checked the DLL with depends.exe without finding any unresolved dependencies.
Is there a way to get more information from Photoshop as to why the plugin fails? Like a "Photoshop Console" or similar?

Yes, at least I think it is correct. I compile it with the same commandline as is used in the "Outbound" example:
#define plugInName "My Test Exporter"
#define plugInCopyrightYear "2007"
#define plugInDescription \
"Test export plug-in module for Adobe Photoshop¨."
#define ResourceID 16000
#include "PIGeneral.h"
// PiPL resource
resource 'PiPL' (ResourceID, plugInName " PiPL", purgeable)
Kind { Export },
Name { plugInName "..." },
Version { (latestExportVersion << 16) | latestExportSubVersion },
CodeWin32X86 { "PluginMain" },
SupportedModes
noBitmap, doesSupportGrayScale,
doesSupportIndexedColor, doesSupportRGBColor,
doesSupportCMYKColor, doesSupportHSLColor,
doesSupportHSBColor, doesSupportMultichannel,
doesSupportDuotone, doesSupportLABColor
EnableInfo
"in (PSHOP_ImageMode, GrayScaleMode,"
"IndexedColorMode, RGBMode,"
"CMYKMode, HSLMode,"
"HSBMode, MultichannelMode,"
"DuotoneMode, LabMode)"

IDCS Win - Error message deciphering

I am debugging a plugin when I come across this line of code:
b if( CmdUtils::ProcessCommand(newWinCmd) != kSuccess)
InDesign spins off this assert:
b Calling Selection Extension Registry::Initialize more than once
followed by 21 occurrences of this assert:
b Collision in lookup
The command completes without a problem, but the plugin crashes once the whole thing is done. Since this is the only place I am getting any asserts, I am guessing that here is where my problem lies. I don't know, however, what the asserts mean.
Does anyone have a clue as to what is going on?
TIA!
John

Please note that I have determined this to be a problem caused by a document remaining open after I had expected my code to close it. See the post with the subject "[IDCS Win] Plugin not closing document" for a fuller explanation.

Cw 9.5 for creating plugins for adobe indesign cs2 in mac 10.4.8

i am new to plugin creations.please anyone give me an basic idea of creating plugins for adobe indesign cs2.
and how to debug the plugin, how to create it using code warrior 9.5, if any one know the site reference please inform me.
thanks in advance
subha

i am new to plugin creations.please anyone give me an basic idea of creating plugins for adobe indesign cs2.
and how to debug the plugin, how to create it using code warrior 9.5, if any one know the site reference please inform me.
thanks in advance
subha

How to set the PSSigGetSigValueParams.sigMode and subfilter for a PubSec plugin

Hi,
My PubSec plugin, based on DocSign sample, has its PSSigGetSigValueParams.sigMode value to kPSSigMethodPKCS1 by default. I am creating PKCS7 signatures, but due to this default value i cannot.
My questions:
1 - My understanding is that to create PKCS7 signatures my subfilter should be adbe.PKCS7.detached or sha1. And i assume that PSSigGetSigValueParams.sigMode value in sigGetSigValue() is also related, but its constant and cannot be set. how can i set the subfilter and sigMode values so that my plugin starts creating pkcs7 signatures?
2 - I cannot find a documentation which would describe the detailed process of creating and validating signatures using PubSec, in the same way it is described for DigSig. Can you point out such a document so i dont have to ask these basic questions?
3 - Is there any sample available which creates PKCS7 signatures?
thanks in advance.

OK... i am answering myself again.
1 - Ans: How can i set the subfilter value for a PKCS7 signature in my plugin
2 - Ans: I still cannot find any detailed documentation. I just debugged the plugin and found out answers for myself.
3 - Ans: And i still dont know if there is any PKCS7 signature creating sample. but if u use the DocSign sample and follow the steps described in 1-Ans above, then you can easily create PKCS7 signatures.
So, i am considering my question answered. hope it helps others aswell.

R3D File Format Not Supported (even after downloading the REDCINE-X plugin) . . . Help!

So I'm currently attempting to import my RED footage into Premier CS4.
I've all ready downloaded the Redcine-X plugin for Premier Pro.
The Problem(s):
(1) My media browser acknowledges the file however, it won't play in my
preview window nor will it import.
(2) I'm not given the RED Format Preset in my New Sequence window
when I attempt to make a new sequence.
I was wondering if anyone knows any solutions and could possibly help
me out, thoughts?

installing REDCINE-X won't do anything for CS4.
you need a CS4 plugin:
REDCODE CS4 Win 1.3.msi
SUMMARY: Provides native REDCODE media (R3D) support for
Premiere Pro CS4 (4.0.1 and later) and After Effects CS4 (9.0.1 and later).
Includes: REDCODE importer (v1.3.0), After Effects Settings Dialog
and workflow guide. Note: Supports RED ONE cameras up through Build 18.
unfortunately, it seems to be gone from the RED site.
hahahahahahaha!!!

Difficulty Loading External Plugins

Is there other issues that might keep an external plugin from loading besides the SWF not being at the http location and the isFrameworkVersionSupported() not returning true? I've got a couple of tracking plugins that I'm having difficulty loading. One is the GTrackerPlugin the other is a third-party tracking plugin. I've overwritten the GTrackerPlugin's isFrameworkVersionSupported() function to always return true and ensured the swf is on the server I'm trying to load it from. The trace statement in the GTrackerPlugin's constructor isn't getting called from the plugin when it's loaded, although I'm not sure it should being that it's loaded externally. It's difficult to debug external plugin hang-ups with only an error event "pluginLoadError". Any guidance is much appreciated.

If it helps, here are my source files for the test project and the GTrackerPlugin with the following minor override in the GTrackerPluginInfo class:
          override public function isFrameworkVersionSupported(version:String):Boolean
               // Force this plugin to load regardless
               // of what version of OSMF we're running
               trace("GTracker version:"+version);
               return true;
GTrackPlugin Project
http://dev.ionflow.net/osmf/GTrackPlugin.zip
GTrackPluginTest Project
http://dev.ionflow.net/osmf/GTrackPluginTest.zip

[SOLVED] Playing sound simultaniously from wine and other applications

I'm using Pulseaudio with the following packages installed:
~> pacman -Q | grep 'alsa\|pulse'
alsa-lib 1.0.27.2-1
alsa-plugins 1.0.27-2
alsa-utils 1.0.27.2-1
lib32-alsa-lib 1.0.27.2-1
lib32-libpulse 5.0-1
libpulse 5.0-1
pulseaudio 5.0-1
pulseaudio-alsa 2-2
When running a wine application sound works, unless a linux application is playing sound. If that is the case, no sound is playing from the wine app until sound from the linux application stops (for example by pausing smplayer).
Is there any way to make sound work simultaneously from wine and native applications?
Other information that may be relevant:
Architecture - x86_64
Desktop - KDE
Wine application - BabasChess
Last edited by CarbonFixer (2014-04-16 16:14:10)

V1del wrote:Install lib32-alsa-plugins and set wine to use the default resp (System Standard) card in winecfg pulsemixers should show an [alsa-plugin] wine stream
Thanks
Was missing that package.

Wine-doors error

HI look my problem
[root@prodigy wine-doors-0.1.1]# python setup.py install
Performing system install with parameters: / /
Installing system base libraries
Symlinking icons
Symlinking executable
Setting permissions
Creating initial preferences
Checking dependencies
wine . . . Found
cabextract . . . Found
tar . . . Found
orange . . . Found
ps . . . Found
No protocol specified
/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
pygtk . . . Found
pycairo . . . Found
rsvg . . . Found
[root@prodigy wine-doors-0.1.1]#
and
[cyber@prodigy ~]$ wine-doors
Created log file: wine-doors.log
Debug: in path: /home/cyber/.wine-doors
Started logging session
Debug: Xoring all/installed to create available
Traceback (most recent call last):
File "/usr/bin/wine-doors", line 92, in <module>
import gtk, ui
File "/usr/share/wine-doors/src/ui.py", line 19, in <module>
import dbus
ImportError: No module named dbus
[cyber@prodigy ~]$
please,
How can I fix it?
Last edited by Piero Ferraz (2008-01-26 16:31:37)

mirosol wrote:
Hi. I'm getting this error with wine-doors...
[mirosol@dhcppc0 ~]$ wine-doors
Started logging session
Checking wine drive: /home/mirosol/.wine/
wine.py: CheckDrive: No wine-drive defined in specified wineroot
Error: No such file : /tmp/System Base.xml
Traceback (most recent call last):
File "/opt/wine-doors/src/ui.py", line 263, in on_bt_proceed_clicked
queue.AddBaseLibraries()
File "/opt/wine-doors/src/queue.py", line 261, in AddBaseLibraries
packlist.Update( repo )
File "/opt/wine-doors/src/packlist.py", line 274, in Update
self.Parse( local_file )
File "/opt/wine-doors/src/packlist.py", line 239, in Parse
parser.parse( xmlfile )
File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 103, in parse
source = saxutils.prepare_input_source(source)
File "/usr/lib/python2.5/site-packages/_xmlplus/sax/saxutils.py", line 523, in prepare_input_source
f = urllib2.urlopen(source.getSystemId())
File "/usr/lib/python2.5/urllib2.py", line 121, in urlopen
return _opener.open(url, data)
File "/usr/lib/python2.5/urllib2.py", line 366, in open
protocol = req.get_type()
File "/usr/lib/python2.5/urllib2.py", line 241, in get_type
raise ValueError, "unknown url type: %s" % self.__original
ValueError: unknown url type: /tmp/System Base.xml
Any ideads?
yes
It is exactly the same problem
please help
[cyber@prodigy /]$ wine-doors
Started logging session
Checking wine drive: /home/cyber/.wine/
wine.py: CheckDrive: No wine-drive defined in specified wineroot
Error: No such file : /tmp/System Base.xml
Traceback (most recent call last):
File "/opt/wine-doors/src/ui.py", line 263, in on_bt_proceed_clicked
queue.AddBaseLibraries()
File "/opt/wine-doors/src/queue.py", line 261, in AddBaseLibraries
packlist.Update( repo )
File "/opt/wine-doors/src/packlist.py", line 274, in Update
self.Parse( local_file )
File "/opt/wine-doors/src/packlist.py", line 239, in Parse
parser.parse( xmlfile )
File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 103, in parse
source = saxutils.prepare_input_source(source)
File "/usr/lib/python2.5/site-packages/_xmlplus/sax/saxutils.py", line 523, in prepare_input_source
f = urllib2.urlopen(source.getSystemId())
File "/usr/lib/python2.5/urllib2.py", line 121, in urlopen
return _opener.open(url, data)
File "/usr/lib/python2.5/urllib2.py", line 366, in open
protocol = req.get_type()
File "/usr/lib/python2.5/urllib2.py", line 241, in get_type
raise ValueError, "unknown url type: %s" % self.__original
ValueError: unknown url type: /tmp/System Base.xml
c^ caught. Quitting.

Photoshop/Mac -- update window bug after plugin completion?

After some of my plugins, photoshop/photoshop elements don't redraw image window (only on Mac!).
Some correlation exists between image scale and this problem -- "Actual pixels" scale repainted (always?) correctly, and any other scale SOMETIMES don't updated.
If user change window size, image redrawed with plugin results.
Work-around found -- send Update event to foreground window during filterSelectorFinish processing.
But where is root of problem?

OK, then HOW is your plugin preventing Photoshop from receiving an update/paint event?
You really need to spend some time debugging your plugin.

3rd party plugins crash Premiere after restart.

Yesterday, everything worked fine. I have a Sequence with clips and have been happily rendering from it for a week.
It has a mixture of Magic Bullet Looks, Film Convert and native effects across a range of clips.
Today, on opening Premiere I find that if any of the 3rd party plugins are enabled I can't render - worse, they crash Premiere.
I have not installed anything or changed anything since I was last using Premiere. I installed an update to the Creative Cloud desktop app this morning, but that was after I started having these issues.
I have tried restarting Premiere numerous times.
Rendering is fine with native Premiere plugins.
System:
Win 7 Pro
Core i7 950
12gb RAM
Quadro FX3800
Running Adobe CC, latest versions

It gets wierder. After the Creative Cloud desktop app was updated it said a whole bunch of programs needed updating so I updated Premiere.
On restart it now wont even recognise the .MTS files it was happily reading earlier.
Apparently it is now an Unsupported Compression Type, which it clearly wasn't earlier.
Windows plays the file fine so this is ANOTHER Premiere issue I'm having now...

Debugging a plugin on a WIN PC

Similar Messages

Maybe you are looking for