On Wed, 5 Aug 2009 23:22:49 +0200, Pawe³ Blokus wrote: > > Only the issue with directory.png and content.png being hard-coded, > > which I think I mentioned previously. If these can be picked up from > > global variables (preferably with full path) that would make things a > > lot more flexible. > > Assuming the front ends would be adding "file://" by themselves so > that it could get removed from core tree,
I see no problem with that. > would two front end specific > #defines be sufficient here? The directory/content icons would be in > one directory with other ones, right? Or is there a need for different > directory icons? I doubt there is a need for different directory icons. The problem with #defines is they are set at compile time, although by setting the defines to my own global variables, that becomes a non-issue anyway, so take your pick! [Select/Scroll widget] Tried this out, and the gadget doesn't display in line with the form object being clicked on - it appears to be lined up from the top of the display down to document co-ordinates. If the doc is at 0,0 then it is in the correct place. If I scroll down the page and then select, the gadget appears at the same place it would if I was positioned at 0,0. You mentioned something about root box co-ordinates previously. If this is working for all other platforms then you might need to shed some more light on how I am supposed to be handling scrolling. :) Regards Chris
