|
|
Julien Charton
|
|
Info:
Title: |
|
Department: |
|
Organization: |
|
URL: |
|
Location: |
|
Region: |
|
Country: |
France |
|
|
Watchlist Changes of Julien:
Tag Cloud of Julien:
Unrecognized action
|
My notes about ICARE
Matlab API
- A message shall be displayed by yapSendCommand when an error occur (same remark for all other functions)
- A command or keyword shall be available in all server to set/read the "log level"
- mmdsvrTestGetImage fails for images > 8000*8000 bytes
labVIEW API
- each VI shall have its own distinct icon
- yapClientConnect : "connexion" output is labelled "bolean"
- the error stack shall be available : the global error handling scheme shall be revisited
- one parameter (connexion id or error stack for exemple) shall be passed from one vi to the other, to help sequencing without exlpicit labview sequence (film strip).
- yapSendCommandData: "buf" output shall be of type "string" instead of double* (string is labVIEW equivalent of C generic pointer void*)
- the yap library in "user lib" contextual menu has a wrong icon and name
- a communication error can crash labview (example: too few data from server)
C/C++ API
- All exported function of yap library shall use types with explicit size (i.e U8,I26,F64...) instead of implementation-dependent types such as size_t or int
- C++ server sometimes freezes. Apparently when client terminates while the server is sending data (TBC)
General
- SETUP/STATUS Keywords are sometimes called "keywords" and sometimes called "parameters" : confusing
- A lot of zombie connexion can remain when a client is being debugged (termination without explicit "yapClose"). A command such as "yapKillAllZombies" shall be available in all environments
My Personal Data
This topic: Main
> TWikiUsers > JulienCharton
Topic revision: r7 - 2007-03-15 - JulienCharton