Unable to run latest CVS snapshot of orca.

Hi all
Today I downloaded the latest CVS snapshot of Orca. I was able to 
successfully build and install it, however when I try to run it, I get 
the following error.

luke <at> marin:~$ orca
Changing debug level to 1000
Changed debug level to 1000
Traceback (most recent call last):
  File "/usr/bin/orca", line 26, in ?
    orca.orca.main()
  File "/usr/lib/python2.4/site-packages/orca/orca.py", line 969, in main
    init(registry)
  File "/usr/lib/python2.4/site-packages/orca/orca.py", line 880, in init
    _buildAppList(registry)
  File "/usr/lib/python2.4/site-packages/orca/orca.py", line 233, in _buildAppList
    acc = registry.desktop.getChildAtIndex(i)
CORBA.COMM_FAILURE

I am happy to help debug/fix this issue, so some pointers would be 
great, thanks.
--

-- 
Luke Yelavich
GPG key: 0xD06320CE 
	 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso <at> themuso.com
ICQ: 18444344

_______________________________________________

gnome-mag CORBA API documentation

Hi Bill,

I'm trying to indentify all the methods that can be called by other 
application to communicate with gnome-mag throw CORBA to document then. 
I find these:

    * GNOME_Magnifier_Magnifier__get_SourceDisplay()
    * GNOME_Magnifier_Magnifier__get_TargetDisplay()
    * GNOME_Magnifier_Magnifier__set_SourceDisplay()
    * GNOME_Magnifier_Magnifier__set_TargetDisplay()
    * GNOME_Magnifier_Magnifier_addZoomRegion()
    * GNOME_Magnifier_Magnifier_clearAllZoomRegions()
    * GNOME_Magnifier_Magnifier_createZoomRegion()
    * GNOME_Magnifier_Magnifier_dispose()
    * GNOME_Magnifier_Magnifier_getProperties()
    * GNOME_Magnifier_Magnifier_getZoomRegions()
    * GNOME_Magnifier_ZoomRegion_dispose()
    * GNOME_Magnifier_ZoomRegion_getMagFactor()
    * GNOME_Magnifier_ZoomRegion_getProperties()
    * GNOME_Magnifier_ZoomRegion_getROI()
    * GNOME_Magnifier_ZoomRegion_markDirty()
    * GNOME_Magnifier_ZoomRegion_moveResize()
    * GNOME_Magnifier_ZoomRegion_setMagFactor()
    * GNOME_Magnifier_ZoomRegion_setROI()

There are others? There is any method that is used to comunicate with 
gnome-mag that don't use CORBA?

Thanks,
Carlos.

Re: Unable to run latest CVS snapshot of orca.

Yikes - I've seen this before, and if I remember correctly,
it's because the AT-SPI Registry is corrupt.  Have you tried
rebooting?

Will

On Dec 7, 2005, at 4:55 AM, Luke Yelavich wrote:

> Hi all
> Today I downloaded the latest CVS snapshot of Orca. I was able to
> successfully build and install it, however when I try to run it, I get
> the following error.
>
> luke <at> marin:~$ orca
> Changing debug level to 1000
> Changed debug level to 1000
> Traceback (most recent call last):
>   File "/usr/bin/orca", line 26, in ?
>     orca.orca.main()
>   File "/usr/lib/python2.4/site-packages/orca/orca.py", line 969,  
> in main
>     init(registry)
>   File "/usr/lib/python2.4/site-packages/orca/orca.py", line 880,  
> in init
>     _buildAppList(registry)
>   File "/usr/lib/python2.4/site-packages/orca/orca.py", line 233,  
> in _buildAppList
>     acc = registry.desktop.getChildAtIndex(i)
> CORBA.COMM_FAILURE
>

Re: [g-a-devel] Unable to run latest CVS snapshot of orca.

On Thu, Dec 08, 2005 at 12:53:12AM EST, Willie Walker wrote:
> Yikes - I've seen this before, and if I remember correctly,
> it's because the AT-SPI Registry is corrupt.  Have you tried
> rebooting?

Yes that helped, thanks.
--

-- 
Luke Yelavich
GPG key: 0xD06320CE 
	 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso <at> themuso.com
ICQ: 18444344

_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list

Re: gnome-mag CORBA API documentation

Carlos:

Thanks very much for your offer to help document the gnome-mag API.  
We're planning to use doxygen to generate API documentation from the 
IDL.  Thus, everything in the file "GNOME_Magnifier.idl" is public API 
and should be documented via the doxygen comment techniques.

This includes GNOME_Magnifier_Point, GNOME_Magnifier_RectBounds, 
GNOME_Magnifier_ZoomRegion_AlignPolicy, 
GNOME_Magnifier_ZoomRegion_ScrollingPolicy,  
GNOME_Magnifier_ZoomRegionList, as well as the methods you list below.

The methods associated with IDL attributes should be documented by 
documenting the attributes directly; you should not create documentation 
for "__get_SourceDisplay", etc.

Please see the recent IDL tarball posted at 
gnome.org/~billh/at-spi-new-idl/idl.tar.gz, and the documentation 
generated from this IDL at gnome.org/~billh/at-spi-new-idl/html/html/
for examples of how to use doxygen comments to document IDL.

Again, thanks very much!

Bill

Carlos Eduardo Rodrigues Diogenes wrote:

> Hi Bill,
>
> I'm trying to indentify all the methods that can be called by other 

Re: [g-a-devel] Unable to run latest CVS snapshot of orca.

Luke Yelavich writes:
> On Thu, Dec 08, 2005 at 12:53:12AM EST, Willie Walker wrote:
> > Yikes - I've seen this before, and if I remember correctly,
> > it's because the AT-SPI Registry is corrupt.  Have you tried
> > rebooting?
> 
> Yes that helped, thanks.

For the record, wouldn't restarting X accomplish the same result? I'm
thinking Ctrl-Alt-Backspace?

I'd hate to see our environment degrade to the primitive resolutions
employed in that other OS ...

> -- 
> Luke Yelavich
> GPG key: 0xD06320CE 
> 	 (http://www.themuso.com/themuso-gpg-key.txt)
> Email & MSN: themuso <at> themuso.com
> ICQ: 18444344

> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

--

-- 

Janina Sajka				Phone: +1.240.715.1272
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Re: Unable to run latest CVS snapshot of orca.

Janina's right of course, just restarting the X server (or logging out!) 
should have solved the problem.

It's probably a good idea to log out and back in after replacing a core 
component like the at-spi-registry anyway.

best regards,

Bill

Janina Sajka wrote:

>Luke Yelavich writes:
>  
>
>>On Thu, Dec 08, 2005 at 12:53:12AM EST, Willie Walker wrote:
>>    
>>
>>>Yikes - I've seen this before, and if I remember correctly,
>>>it's because the AT-SPI Registry is corrupt.  Have you tried
>>>rebooting?
>>>      
>>>
>>Yes that helped, thanks.
>>    
>>
>
>For the record, wouldn't restarting X accomplish the same result? I'm
>thinking Ctrl-Alt-Backspace?
>

Re: gnome-mag CORBA API documentation

Bill Haneman wrote:

> Carlos:
>
> Thanks very much for your offer to help document the gnome-mag API.  
> We're planning to use doxygen to generate API documentation from the 
> IDL.  Thus, everything in the file "GNOME_Magnifier.idl" is public API 
> and should be documented via the doxygen comment techniques.
>
> This includes GNOME_Magnifier_Point

What is this struct for?

Bill, can you give some informations about the AlignPolicy and 
ScrollingPolicy structs?

Thanks,
Carlos.

tasks division between gnome-mag and gnopernicus

Hi,

I find strange have an API markDirty in the gnome-mag IDL interface.

The responsability to verify the regions that get dirty (it's the same 
as damaged, isn't is?) ins't is exclusively of gnome-mag? There are 
cases, where a client application, like gnopernicus, will use it?

Thanks,
Carlos.

Re: tasks division between gnome-mag and gnopernicus

Carlos Eduardo Rodrigues Diogenes wrote:

> Hi,
>
> I find strange have an API markDirty in the gnome-mag IDL interface.
>
> The responsability to verify the regions that get dirty (it's the same 
> as damaged, isn't is?) ins't is exclusively of gnome-mag? There are 
> cases, where a client application, like gnopernicus, will use it?

Yes, sometimes.  It's not something commonly required, but in some cases 
a client may know about changes that the magnifier does not.

Bill

>
> Thanks,
> Carlos.
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel