-i time.
to' argument.
list()
return type but converters only apply for primitive type.
Convert primtive to S object for return.
*toolbar, we get .*toolbar:.
Problem is in creating a resource without checking the name for
a qualifier.
> tmp = getResourceList("XmList")[[1]][["itemCount"]]
> tmp@class
[1] "Int"
> lookupConverter(tmp@class)
[1] "Long"
res = getResource(draw,XResource("width",1),XResource("height",1))
gives an error I think.
and gives a SIGSEV later on (next event!)
Wrong type as there is no converter from HorizontalDimension to
integer. NULL instead of 1 works.
lookupConverter("HorizontalDimension")
[1] "Long"
new(class-name) (e.g. new("Widget"))
sapply(.StandardWidgetSets,load.WidgetSet)
Problem: Internal error: data for decrementing ref. count didn't point to a
valid arena (0x85c2080)
but
sapply(.StandardWidgetSets,function(x)list(a=1,b=2))
is ok.
s_name_table *
rather than s_object * from
create_?_class_table.
This should go away with Pthreads, I think as the event loop will be in its own thread.
S_alloc() and set_alloc().
See add_callbacks in XCallbacks.web.
Check this works. Seems to cause
some problems.set_widget_user_data().
validObject(). Call isValid() instead.
XTree and DisplayTree().
use r = getResource(other top-level widget, x=1,y=1)
and then use these values
r[[1]]@value = r[[1]]@value + 10
r[[2]]@value = r[[2]]@value + 10
in setResource(new-widget,r)
Should be able to do this at the S level given the database functions. In fact, these should automatically get picked up!
Is this the problem with the device not working at all. If so, that was fixed by fixing the flags to not use push backs which John started using at one point on the generic class of connections unaware that there were X connections that behaved differently.
XSendEvent() function.
This can be handled neatly with threads. The callback (or any function in general) starts by calling a function something like this
completionStatus("obj-name",lock=threadLock-object,
total=total-length,widget=application,method=basic-update)
This functon spawns a new thread by constructing the following
sort of expression which is to be evaluated by that the thread
dpy = createStatusDisplay(0,total,widget) # create the status bar
setCursor("watch", widget) # set the cursor to signify busy
finished = F
while(!finished) { # do an endless loop an
obj = get(obj-name,where=threadLock-object)
n = length(obj)
updateStatusDisplay(n,total)
if(total==n)
finished = T
wait(threadLock-object, obj-name)
yieldLock(threadLock-object)
}
removeStatusDisplay(dpy)
The mechanism this second thread uses is to watch for
assignments to the relevant object and then compare the current
length of that object with the target length.
This generalizes to multiple threads performing the computations
and all assigning to the the same object.
The updateStatusDisplay()
If the length of the target object is constant because it is pre-allocated, a more elaborate test such as counting the number of non-null slots can be used.