Closed GoogleCodeExporter closed 8 years ago
It looks like flourescence is not able to determine what object is currently
under the mouse position. I'll try and test it on a current Ubuntu version and
see what I can do about that.
The thing with the tons of output is mostly related to faulty muls. For
example, the often occuring message "Using artId without animdata for
animation: 6043 179b" means that the tiledata info for 0x179b indicates that
this item should be animated (flags), but there is no animdata block for it.
In one of the next versions I'll add some more information to "Trying to access
out of bounds index=29287 size=16384". What it basically means is that you are
trying to read data block 29287 from an idx/mul file pair that has only 16384
index entries.
Original comment by spin@fluorescence-client.org
on 24 May 2012 at 7:07
Testing now with fedora 17 64bits and continue to get same error.
Original comment by iurigu...@gmail.com
on 8 Aug 2012 at 2:01
Unfortunately, I could not get the client to run in an Ubuntu VM, so it is a
bit more challenging for me to reproduce/test this...
Could you please try to compile and run the clanlib example
Examples/GUI/GUICustomComponent? The GUI_Texture example could also be
interesting.
You find the directories in your clanlib/Examples folder. Only make and execute
should be required to run it.
This is to check if there is some issue with clanlib in general, or if it is
just a client problem.
Original comment by spin@fluorescence-client.org
on 8 Aug 2012 at 9:31
With GUICustomComponent i get toolbar in diferent place.
GUI_Texture I can't close the windows.
Original comment by iurigu...@gmail.com
on 8 Aug 2012 at 12:49
Attachments:
Now I am using UOML with no updates and it works well. Looks like the problem
was related with UO version.
Original comment by iurigu...@gmail.com
on 10 Aug 2012 at 3:34
Attachments:
That's interesting. Did you change anything else on your system? Because the
clanlib examples are definitely not affected by your UO version...
But glad to hear it works now :)
Original comment by spin@fluorescence-client.org
on 10 Aug 2012 at 3:42
No change and the examples of clanlib still not closing the windows examples of
GUI_Texture and nor well positioning of toolbar from GUICustomComponent
Original comment by iurigu...@gmail.com
on 13 Aug 2012 at 4:57
I am currently in a live Ubuntu 12.04 environment, and I can't reproduce this
issue.
The windows in GUI_Texture are not closable, but that seems to be intended by
the devs. All other components react correctly to the mouse (e.g. blue color
when mouseover, etc). Also, the custom component appears at the correct
position.
The buttons in both fluorescence and the clanlib examples should change their
appearance when you move the mouse over them. Do they do this correctly?
Can you move the windows around in the GUI_Texture example? If so, do the
components inside the window still react correctly to the mouse?
Are you using any unusual input devices? Do you have maybe more than one input
device attached to your pc, e.g. graphics tablet, joystick, gamepad, etc.
Did you make notable changes to your desktop environment? E.g. install some 3rd
party patches, or a special custom theme?
Original comment by spin@fluorescence-client.org
on 13 Aug 2012 at 8:53
GUI_Texture is working very well here. Only 'x' button that have no effect
(that appears to be right). The only problem that exist is the
GUICustomComponent about toolbar localization. Mouse over 'spells' reacts OK
(nothing wrong in reaction of mouse in).
About input device I have touchpad of laptop and a USB mouse. And a USB
keyboard becouse the laptop keyboard have some problems (2 keyboards + 2
mouses).
My system is almost in default. Only ClanLib with your 3rd part patche.
Original comment by iurigu...@gmail.com
on 13 Aug 2012 at 2:49
Okay, I think I'll just close this issue for now.
Should you ever experience something like this bug again, please add another
comment. But I really hope I do not have to investigate this weird clanlib
behavior any further ;)
Original comment by spin@fluorescence-client.org
on 13 Aug 2012 at 6:39
Original issue reported on code.google.com by
iurigu...@gmail.com
on 24 May 2012 at 1:23Attachments: