te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>java - Why does not using the Event dispatching thread cause a deadlock? - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>java - Why does not using the Event dispatching thread cause a deadlock? - Stack Overflow

    java - Why does not using the Event dispatching thread cause a deadlock? - Stack Overflow

    programmeradmin3浏览0评论

    I have read this thread and verified that it results in a deadlock (JavaSE-22). However, I simply cannot figure out why. Can anyone kindly explain what exactly happens? I know that we are NOT supposed to do it, but I wish to understand what goes wrong.

    I've checked that the constructor actually finished running, and yet text.setText() gets blocked on something. It appears that either of window.pack() or window.setVisible(true) suffice to cause the deadlock. I experimented with wrapping one or both of add(text) and updateGui(); in a SwingUtilities.invokeLater, and it only works when both are wrapped. Of course, in doing so the window.pack(); fails to do what we want, but right now I'm just trying to understand why there is a deadlock in the first place. My expertise is in multithreaded programming and I know very well how deadlocks in general happen, but cannot understand what Swing is doing here. What are pack and setVisible and setText doing that together contribute to the deadlock? I can think of a hundred and one ways, but none of them really make sense to me because I don't see why it should be designed that way at all!

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论